Hi Michael

INLIST can climb if the user starts selecting large numbers of items. I haven't worked out the cut off point but it is resonably high.

In the program I have been working with I allow the users to select the products they want statistics for from a _supermover object. I then build an INLIST statement along with a few other filters and SQLEXECUTE(). Typically, they only select a few products (1-20) which is fine but they can work the other way and include all items (600+) and exclude a few items. It is relatively easy to swap these and use NOT but there is a middle ground that I cant do at all.

What I am looking for is a better way of handling it (and other complex selection filters) on remote VFP databases. When working directly with the tables one can use joins on cursors but at this stage I have found no simple way to do the same on a remote table

Regards
Geoff Scott

>Wow...that must be one hell of a string.