>>Jerry;
>>
>>Have you actually gotten Visual Basic to add a new record to a table that has fired the stored procedure? I agree with you that without VFP running, a VFP stored procedure should not fire.
>>
>>Bob
>
>I'm not so sure I agree. Using ODBC and with the appropriate DLL (VFPODBC.DLL, I think), I don't see any
>reason why it wouldn't. Also why provide access to the DBC via a driver and not allow triggers, stored
>procedures, etc. to behave as they should?
>
>I haven't tried this yet, but I will and if this does work, I'll post it.
>
>George


Hi George;

I haven't tried the VFP ODBC drivers (I mean, who needs to access Fox data using some kind of 'weaker' engine, he?) but I do remember doing it with Powerbuilder against some fox 2.6 data. Apparently some of the indexes were defined with Fox expressions and none of these would update because the function calls couldn't be located. Only indexes that didn't use functions could be updated. It makes sense because the ODBC driver would have to 'understand' a lot of potential commands and functions (Deleted()) was another killer, and who hasn't used that?)

I don't expect fox functions to be supported by ODBC but it sure would be nice. But if I'm going to use ODBC (no Rushmore either) then I will go against SQL Server. And I won't use Acess against my data either (why get a boy to do a man's job?)

Good luck. And let me know if it does work.

Bob