We have an in house MTDLL using SOAP calls to talk with it. The MTDLL is all VFP code, but 12 systems touch this DLL once a minute from a desktop application to update the toolbar. It is also used to add and update records in 7 or so tables. Without using the SYS(2336) we would occasionally get errors that a table could not be found, or could not be updated because it was read-only. We've since added the SYS(2336) around all open and writes to tables and the problem has stopped (knock on wood).
I think this is the OS multi-tasking interrupting a thread long enough during an open/write/select statement to block the second thread from correctly accessing the vfp tables. Tracy -----Original Message----- From: Profox Sent: Wednesday, July 26, 2006 4:30 PM Subject: Re: multithreading in VFP > When opening a VFP table in a MTDLL, use of the Critical Section > Support > SYS(2336) is helpful (see Calvin's blog entry). > Does anyone know if it is required when writing to an index table? Does > anyone recommend it during writes? I don't know if I read the same article and as I recall he didn't go into what would happen if you didn't use SYS(2336) with his ThreadClass in the example he was posting. I got the impression because he was creating a table, not writing to it as of yet, that using SYS(2336) would keep the code from writing to a table that had not yet been created. At any rate, it's all over my head. The code I've written for VFP COM has pretty much been standard VFP code. Jim Eddins _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
