>
>Well... where was your Bottle Neck? What type of Server PC, how much memeory... how many hits were the COM object taking... Did you host the COM Objects in MTS? Or, did you use FoxISAPI... if you are using FoxISAPI you are not were not using the MTDLL's of SP3 since FoxISAPI uses Single USE .EXE COM servers. I believe with FoxISAPI Rick recomends 2 .EXE's per CPU. Did you use Ricks enhanced FoxISAPI?


The bottleneck was that the memory in the server sky-rocketed. I'll be doing some performance testing today w/INETLoad, so I'll have some better metrics later, but I think it was dying w/about 5 users logging in. The server only had 128Meg (we'll be boosting that today).

We did NOT use FoxISAPI... In fact, I'm *sure* that if we did, the application would have been fine. Instead, we're using VFP 6sp3 COM object by themselves and instatiating them directly from ASP.


>
>I believe Rick's model site, Suplus Direct proves that you can write a high traffic site with Web Connect... Have you read the section in Ricks Book about Large Scale Web Sites?

Yes, Rick's model site was done using a FoxISAPI/Web Connect type setup. I *KNOW* that this works. We didn't use that approach. Instead, we were trying to use VFP COM alone. That is the question I am trying to get answered here... Does VFP COM 6sp3 scale as well as was hinted at in Rick's book, and does anyone else have similar experiences?

>>Any insight would be greatly appreciated!
>
>HTH, But need you to answer some of the above questions. You really need to determine what your bottle neck was... It certainly wasn't FoxPro.
>
>BOb