>I have a web program that is using a vfp com component with asp pages. The component was built as multithreaded, and is running on a windows 2000 server with duel processors. The component is opening and accessing about 30 tables over a 100mb network shared(both reading and writing on various tables). My problem is, when I have about 200 concurrent users accessing the web and using the dll, it sends the utilization up to 50% and locks the machine forcing me to reboot about every 2 hours. Has anyone else experienced similar issues?, is this a threading issue?, or do I need to issue any other set commands besides exclusive & resource to manage it. I would appreciate any help on this. Thanks.


Did you install the component as a COM+ application? If so, are you using it stateless? Do you call oContext.SetAbort() or oContext.SetComplete() to tell COM+ that you're done with the component?