>I see from the new thread in the Database section that you're getting the same errors without the inheritance so that's ruled out anyway.
Exactly.
>I also see from the other thread that you are, in fact, getting the same errors with inline VB code. I'd be surprised if you weren't since the compilation is the same whether you use that or code behind files.
Correct.
>Using code behind file for VB. Simpler SQL than yours (just one join). Web server is a slowish W2000 server - only handles about 2500 hits/min. Still using ASP.NET v1.1.4322. VFP data is on the webserver. IIS is 5.1 (I think). Using MS WAST for stress testing (10 threads with 10 sockets/thread) on one client. No errors over a couple of 15 minute runs (and several shorter ones)....
I started to migrate to SQL Server last night. I don't have the full migration ready. But, I ran two sets of tests for 20 minutes each. The SQLClient provider is extremely fast as oppose to the VFP OleDb provider. So, I was able to send three times more hits. I didn't have one single error. This leads to the initial observations that the VFP OleDb provider is not capable to drive at such of number of hits. But, I will have to do a full migration and see how it goes. BTW, I was able to simulate it all on my development PC as well. It just takes more time as it is slower.
>You mentioned that the new server has a dual-core processor. There were some problems with MSSQL and dual-core (but I think it was mainly a speed issue) and, IAC, I assume you're getting the errors on other (none dual-core) servers.
Yes, I got it on three servers. Two of them are Windows Server 2003 and one is Windows Server 2000. My development PC is Windows XP Pro. I get the same situation everywhere.
>Since I'm not getting any errors it would seem that a configuration setting might be responsible but can't think what it might be.
That could be. But, I would still be interesting to have the same set of code, from the ASPX page, with test tables and using my test VB.NET application to see how it goes on your site, if that would ever be possible for you to do.
>I believe your using NET2/VS2005? What OS and IIS version on the web server?
>Does you VFP data reside on the IIS machine?
This is Windows Server 2003, thus IIS 6. The data is under the Web site root under App_Data. So, everything is on the same box. I use .NET 2.0 and we have the latest of everything.
>If you don't have the WAST (Web Application Stress Tool) it's worth getting since it can give a lot of information on the server load itself (It's a free download from MS)
Well, what I have right now does exactly what I need. If I cannot get past that point, there is no need for me to test with another set of tools.
Thanks for your help
