limiting browse based on login?

[Joe Chasan]

you only need "lookup -" if you want to go to that record for update or
similar.  "lookup -" moves the current record pointer to that record.  if
you are not going to update it it may not be necessary to use "-".  a
regular browse lookup should do it.

i don't know what your criteria are for associating a record with a
particular login.  maybe you need a reference file to cross-reference 
unix user login (@id) with customer # field or some other similar field
in that file.  

once you figure that out you can decide if there is an index with which
you can restrict the selection or not - if not, when you define a lookup
via <F5> you will see a prompt for "Processing Label" - this section of 
your prc table gets executed for every record in the index before it gets
displayed.  you create a section of your process table with this label, and
its flow must end with an "end" statement - in it you can do lots of things,
but the main thing you are after in this case is some conditional logic
based on lookupfile(field) that an tell you whether or not to issue 'drop'
command - which will prevent the display of that record in the lookup
browse screen.  (e.g. if: lookupfile(5) ne "XYZ" then: drop)

-joe

On Mon, Aug 31, 2009 at 03:30:26PM -0400, scooter6 at gmail.com wrote:
>   Joe,
> 
>   I have a general idea what you're saying....in fact I made a 'dummy' file
> and added
>   some @menu processing to browse records from the 'main' file, etc.
>   I'm still not certain how I would limit the lookup to just their data?
>   I'm also not certain how to write a lookup to another file when in @menu
>   processing......all I see is a 'dash' lookup in the examples I've seen in
> the manual
>   how do I lookup to another file?
>   Still trying to figure this out - ughh  haha
> 
>   thanks again
> 
>   Scott
> 
> On Mon, Aug 31, 2009 at 10:05 AM, Joe Chasan <jchasan at gmail.com> wrote:
> 
> > I am not near a computer with filepro right now, but the basic idea is
> > this:
> > Call clerk on a file and have processing take over immediately, either with
> > @menu, or with -xe/@entsel combo.  In that prc, prompt for input search
> > criteria - search key and search method if applicable.  Take that info and
> > use it in a browse lookup processing line.  How you drop non-user-specific
> > records is on you then.  If you are lucky, index may help, if not, use the
> > prc= part of lookup to use drop processing.
> >
> > That's a simple browse display - you can add popup screens to that pretty
> > easily.  since it is view only, you don't need to take it further than that.
> >  Also, if it is view only - suppose it doesn't even matter what fp file you
> > run this out of.
> >
> > -joe
> > Sent from my Verizon Wireless BlackBerry
> >
> > -----Original Message-----
> > From: "scooter6 at gmail.com" <scooter6 at gmail.com>
> >
> >  Date: Mon, 31 Aug 2009 09:42:25
> > To: <joe at magnatechonline.com>; scooter6 at gmail.com<scooter6 at gmail.com>;
> > filePro Mailing List<filepro-list at lists.celestial.com>
> > Subject: Re: limiting browse based on login?
> >
> >
> > _______________________________________________
> > Filepro-list mailing list
> > Filepro-list at lists.celestial.com
> > http://mailman.celestial.com/mailman/listinfo/filepro-list
> >
> >
--
-Joe Chasan-                           Magnatech Business Systems, Inc.
joe - at - magnatechonline -dot- com   Hicksville, NY - USA
http://www.MagnatechOnline.com         Tel.(516) 931-4444/Fax.(516) 931-1264