>The best way to handle this is to use abstract connection, data and idgenerator classes that handle differences internally but provide the same exposed methods and properties (interface) to the interface or business tier.

Will,

Thank you for the detailed response. Abstracting the data access into classes definitely seems like the best way to go. At this point, we are just going to evaluate whether or not we want to go down this road or possibly jump on Jim's bandwagon and ditch VFP's data engine entirely.. Decisions decisions.. Regardless, though, I do like the idea of the data classes.

You going to Ft Lauderdale? I'm flying down on Sat out of Newark.

Laterness,
Jon