Hi Jason,

I think the problem I'm having is that I need to use functions recognized by regular SQL when using the SQLexec function. SQLexec would have the same problem with InStr() as it would have with at(). Also the remote database may not always be ACCESS.
As Al suggested, the where ...in clause should work, but I seem to be doing something wrong...

>Hey Ashly,
> For your AT() solution in ACCESS take a peek at the InStr() function in help. Not sure if it will do what you need, but may be a bump in the right direction.
>
>'InStr([start, ]string1, string2[, compare])
>
>lsString = "ABCDEFG"
>lnRetVal = InStr(1, lsString, "DEF")
>
>'lnRetVal will = 4 in this case.
>
>Also, I’m not sure if this applies in Visual FoxPro, but I remember reading somewhere that Filters and Indices with a "NOT" are not RUSHMORE Optimized. Don't know if there's any truth in that, but personal preference, i try to avoid em if at all possible...