Then it sounds like you need to turn on some logging to the SQL-Server... maybe via ODBC logging if thats how the transactions are being sent, then you could look in there... It's been quite a while since I've had to do something like that, but I know such a thing exists, and maybe someone else can chime in on more specifics...

A start (if via ODBC connections), open Admin Tools, then Data Sources (ODBC). On the tab dialog window is a "Tracing" page. then set the output log file, and a checkbox for "machine-wide tracing for all user identities" may help... If you want to go further, you can apparently hook the tracing to your own dll, but thats beyond my experience.

Hope this helps get you a bit further to your reverse engineering calls.

>Don,
>
>The DOS program is not an old FoxPro/DOS program. But, rather it appears to be a DOS batch program that has been compiled into an EXE. The program is just a simple data input screen that collects data, passes the data to a several stored procedures and eventually posts it into an old MS SQL 6.5 database. Eventually, I want to try and determine what stored procedures are being called by the EXE and just replace the DOS input screen all together but, until then, I'm going to pass data from the VFP9 forms to the DOS window. Like I said in previous note, I have that working but would like to have the DOS screen embedded (attached) to my VFP9 form, if that's even possible.
>
>Thanks,
>Robert
>
>
>>Don't know about that, but what about just reading the FoxPro DOS tables >directly and pushing whatever data you need directly into the old tables... >VFP will respect the old format.