limiting browse based on login?

[Ken Cole]

Tom,

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.
>

I have always found the "drop all before" and "drop all after" work
extremely well and stops filePro from checking any more records which is why
I wasn't sure why the original request wasn't done in a browse on the
original data file using both these commands.  It makes this sort of
functionality simple, quick and clean.

Ken
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.celestial.com/pipermail/filepro-list/attachments/20090904/a64f502b/attachment.html