limiting browse based on login?

[Tom Aldridge]

scooter6 at gmail.com wrote:

>   I only have 1 client at this time that I'm building this for, but it will
> be used more
>   and more as I have heard we have several clients that have requested this
>   functionality......
> 
>   But, for this project, just 1 client and they will have about 600 records
> in
>   the "browse lookup" file out of approx 550,000 so it does take a bit to
> load
>   just their records based on the 'drop' processing I'm using.....

Hi. Are you the original poster on this? Anyway... not to just beat the 
drum over again on the qualifier thing, but now that I know you 
presently have one client who wants this and more on the way, I think 
maintaining the records at all times in the qualified files (vs the 
original suggestion to copy to the qualifier on the fly) would be nice 
and fast and clean. Browse processing is great for a many things 
including dropping records, but as you know,  not so when it comes to 
dropping lots and lots of records.... because it's reading every record 
and making a drop decision vs using an index.

Depending on what you anticipate for the number of future clients vs any 
sort of filePro limitations to qualifiers, you could have each client 
work out of THEIR qualifier, and if you need to combine the various 
client records back into the main file, then do so as they create, 
update or delete their qualified records.

What do you think of that?

Tom Aldridge