>>yeah, I noticed that EXECSCRIPT() was supported in VFPOLEDB after I decided to abandon the SP route. Guess it could have been made to work there.
>>At the moment I'm going to a combination of using VFPOLEDB and a COM DLL. The former for the simple data retrieval into VS tables and the latter for the awkward bits like memo retrieval and the places where I can make good use of the existing VFP class libraries.
>
>Depends on how frequently you need to call this, because execscript() creates a .prg and then .fxp every time it's called. Not quite sure when these get deleted, if ever. So speed may be an issue, and perhaps garbage too.

IAC, thinking about it: if VFPOLEDB doesn't support a command then using it in EXECSCRIPT() would also fail anyway ?