M
Michael Rutherford
I have an application that is being upgraded from Microsoft Access. I
have converted the data tables to SQL Server. We are still using the
Access front end to connect from remote locations. Because of a slow
network, the application performance is unacceptable.
It takes over 40 seconds to move from one record to the next.
Instead of rewriting the application in ASP.NET, I am considering
using OWC to implement a 3-tier architecture as described in
http://msdn.microsoft.com/library/d.../en-us/dnacc2k2/html/deploydap.asp?frame=true
Does anyone have specific experience with this? Will the ActiveX
control load up and communicate effectively with the web server? Will
I get the performance gains that I need?
have converted the data tables to SQL Server. We are still using the
Access front end to connect from remote locations. Because of a slow
network, the application performance is unacceptable.
It takes over 40 seconds to move from one record to the next.
Instead of rewriting the application in ASP.NET, I am considering
using OWC to implement a 3-tier architecture as described in
http://msdn.microsoft.com/library/d.../en-us/dnacc2k2/html/deploydap.asp?frame=true
Does anyone have specific experience with this? Will the ActiveX
control load up and communicate effectively with the web server? Will
I get the performance gains that I need?