Hello -
I'm trying to find some answers to a problem which seems very common with this product. We are constantly having problems with slowness while using ASP.NET, ASP, and MSACCESS to query data from QB Enterprise 7. I've followed the ASP and .net "Remote Connector" instructions and have even spoken to flexquarters support about this. Some days, it works ok - slow, but returns data. Other days, the whole process hangs, some tables query fine, while others hang the browser, MSACCESS and even the QB server needs to be reset sometimes.
Has anyone found a solid way to make this work consistantly? Are we just trying to pull too much data or does QODBC break when trying to query big tables? Has putting QB on a dedicated server helped anyone else? It does not seem to take much network or hardware resources, but perhaps it's one of those apps who wants a server it all to itself? Right now it's running on our file server which does not see a tremendous amount of traffic.
i've heard that running QODBC server edition using DCOM and having a copy of QB running on each web server might improve performance, but we have a large web farm and this could be a nightmare.
I really appreciate any help, but please don't link slap me to another forum unless it directly addresses the problems I've mentioned above. this can make others viewing the post think it's resolved.
Many thanks! |