limiting browse based on login?
Boaz Bezborodko
boaz at mirrotek.com
Tue Sep 1 13:32:21 PDT 2009
Let's see if I can summarize the steps you need to take.
If you can make sure that the system holds a variable to hold the user
name then you can build a new file with the information of which
customers that user can review. (This will give you the ability to
expand this for future customers. Simply add records with new user
names and the customers they can view.) Then, when you do a browse
lookup, you DROP all the customer records that are not allowed so they
can only see the ones they are allowed to access.
To keep them from accessing IUA you need to enter processing in an @MENU
routine that allows the user to navigate through the records they are
allowed to view. You can use LOOKUP - to move to the records you need.
To update you will need to generate PUSHKEY keystrokes to go into update
mode before ending the @MENU routine and then you might need an @UPDATE
routine to control what happens once they enter update mode.
> Message: 4
> Date: Tue, 1 Sep 2009 15:16:48 -0400
> From: "scooter6 at gmail.com" <scooter6 at gmail.com>
> Subject: Re: limiting browse based on login?
> To: joe at magnatechonline.com, "scooter6 at gmail.com"
> <scooter6 at gmail.com>, filePro Mailing List
> <filepro-list at lists.celestial.com>
> Message-ID:
> <445ca8160909011216r300496b5o79d6a574078de88d at mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> I guess I'm still not getting it.........
> In the "main"file, there are records associated with different clients.
> In this particular instance, client number 4764 needs to have access to
> our
> system via ssh to just VIEW their records, along with asociated notes that
> are
> made on their records (these notes are contained in a separate file where
> currently on our system there are browse windows created on screen 2 for
> us to
> see the notes, etc.
>
> So, in playing around with @menu I have created a file that has 2 dummy
> fields
> in it. So, if I now go to IUA and choose this "new file" it gives me the
> option to
> search by name or account number (the 2 dummy fields I created)
> However, when I do the @menu processing, it still shows ALL records in the
> "main" file. I can't figure out how to do the browse lookup to the "main"
> file and
> only show the records that belong to them. How would I accomplish this?
>
> My 2nd alternative I'm playing with is simply creating a "new" file and
> copying just
> their records to it nightly and creating 2 screens for them to view notes,
> etc.
> That is the "easy" way out, but not really how I want to do this in the
> event I have
> future clients that want to also be able to see their data, I would like
> to have a
> "solution" in place. I'm just stuck on the lookups and limiting them to
> seeing
> just their data.
>
> They will have their own unique login, but I don't see how I would tie
> that in to
> limiting the records they see unless I do what I just mentioned above and
> create
> a new file for just their records?!!??! uggh.....lol
>
> Scott
>
>
>
> On Tue, Sep 1, 2009 at 9:24 AM, Joe Chasan <joe at magnatechonline.com> wrote:
>
>
>> 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 <http://www.magnatechonline.com/>
>> Tel.(516) 931-4444/Fax.(516) 931-1264
>>
>>
More information about the Filepro-list
mailing list