Hello,

I have an intranet application running on a W2k server SP2 with IIS5.0. I upgraded from mdac 2.1 to 2.7, installed JEt4.0 and the .NET framework. Most of my db quering pages work kept working fine. Others took ages to execute their queries, resulting in a script-timout. restarting IIS5.0 is the only thing left.
Is there something I should change in my connection strings? I mostly use ODBC DSN and some ADO strings like :
MM_Winkelbezoek_STRING = "Driver={Microsoft Access Driver (*.mdb)}; DBQ=C:\inetpub\wwwroot\intranet01\_private\winkelbezoek.mdb

Did/does anyone have the same problems?

Grz Karz

Cant help much as but that's a great name for a database.<img src=../images/dmxzone/forum/icon_smile_approve.gif border=0 align=middle>

PS..

You can increase the script timeout in IIS5 easily...

Hehe thx..it's Dutch.. I could increase the timeout , but it doesn't solve the problem. Eventually the dllhost.dll eats up all resources.