limiting browse based on login?
Bruce Easton
bruce at stn.com
Tue Sep 1 18:07:25 PDT 2009
Scott,
Assuming that you want to stay with a character-based solution for this, and
assuming that you already have a way to prevent your ssh'ed users from
getting to anything on your system other than what you intend them to get
to, then I can still think of questions that should be answered before
suggesting a solution.
1. Is the client number always represented by the first four digits of you
master file's key number (the one that you described earlier as having the
format "1234-0001")?
2. How many automatic indexes do you have available?
3. How many ways (sorts) does the user need to be able to browse the data?
4. Is there a need to allow the user to do their own filtering? (Like when
you use and index and a selection set at the same time.)
5. If an index gets blown and causes a user to see something they are not
supposed to see (because it is residing in the same file), what is the
impact?
I'm sure there are more.
There are some useful character-based filepro browse lookup specifications
that could be part of what you need (see "mlen" and "m" [as in "-nxm"] and
"drop", as Joe mentioned, and the various flavors of "drop"). Appropriate
use of these should allow your users to efficiently browse the data the way
you want, but you would still to control the navigation between the browse
lookup and update of an individual record. (Maybe use the technique Joe
described using lookup -. But if not that, then you'll likely wind up
controlling the entire record viewing/updating function with a popup screen
[from @menu or from a newly-created control record].)
Bruce
Bruce Easton
STN, Inc.
________________________________
Scott On Behalf Of scooter6 at gmail.com wrote
Tuesday, September 01, 2009 3:17 PM:
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