Article ID: 191967 - Last Review: August 6, 1999 - Revision: 1.0 PRB: Visual FoxPro In-Process Servers Do Not Run Concurrently
This article was previously published under Q191967 On This PageSYMPTOMS
When a Visual FoxPro 6.0 Component Object Model (COM) component (DLL) is
accessed by multiple threads (or processes, if the Visual FoxPro component
is part of a Microsoft Transaction Server package), if one thread calls a
method on the component while another thread is already executing a method,
the new method call will not begin executing until the existing method call
has finished.
CAUSE
In the object implementation in Visual FoxPro, entry into the run-time is
blocked while another object is in execution.
STATUS
This behavior is by design.
MORE INFORMATION
In order to preserve data integrity of variables, Microsoft Visual FoxPro
blocks entry into the run-time while another object is in execution.
Steps to Reproduce Behavior
Notice that the FastHit does not start until after the SlowHit completes. | Other Resources Other Support Sites
CommunityGet Help NowArticle Translations |






Windows Live
Facebook
Twitter
Linkedin
Digg it
Yahoo
Delicious
StumbleUpon
Yammer
Reddit
Technorati
FriendFeed
Email

Back to the top
