That's how I handle it too. You can actually create a standard interface and class out the different behaviors between data sources pretty successfully. Then you just use your wrapper or behavior classes, and you still get to use a standard set of calls to perform your operations.

I actually extended this idea a bit to handle some of the differences between server backends as well (i.e. SQL vs. Oracle).

>Eric,
>
>I've changed my code to run native VFP SQL statements if the data engine is either native VFP or VFP ODBC. It's also a bit cludgy, but it works.
>
>Thanks for jumping in with this.