>>>Did you check "Multithreaded Server runtime" in the setup wizard? Otherwise, VFP6t.dll will not be installed.
>>>
>>
>>Hi Erik,
>>
>>Would I have to check the "Multithreaded Server runtime" in the setup wizard when the DLLs I have built are single threaded?
>
>Hmmm... No.
>
>
>>Perhaps you can also help me with the difference between the two. Based on what I have read, and the samples I have seen, single threaded is the way to go. A little more memory intensive, but better performance, I thought.
>
>Sheer performance-wise, you'll get more throughput with a ST dll, but an MT dll can help the
perceived performance because a fast hit won't get caught behind a slow one.
>
>A statelessly built MTDLL that takes advantage of transactions running in MTS can also help overall performance because supposedly, MTS can pool the servers, but word is this isn't currently working the way that it should.
>
>>
>>The thing is that the setup installs a working web app on one IIS server, but not on another...? Granted, the working server had the VFP runtimes installed once before, I believe.
>
>VFP6t or not, the runtime seems to be the issue here.
Hi Erik,
Thanks for the followup. I am going to build a new setup from a clean install of VS we just put on a new development machine with SP4. I will then try that on the two web servers. I am going to include the Multi-threaded runtime, just in case.
Thanks again,