In a .prg you can create subclasses of the stock VFP data environment and cursor objects extending them with all kinds hooks and custom functionality. Doing so, I was able to create generic data classes to work with SQL Server via stored procedures. For example, when I call the custom update method on my cursor objects, they automatically know which SP to call, what parms to pass and how to deal with dirty reads and ODBC return errors.

Basically:

DEFINE CLASS bseCursor AS CURSOR, or DEFINE CLASS bseDE AS DATAENVIRONMENT

- the rest is up to your imagination. There seems to be no limit to what you can do.

I will be happy to share these ideas with anyone. Just give me your email address and I will send you the code.

Charlie