DBinPhilly
05-16-2011, 01:19 PM
In a network with about 18 workstations, the MS Access is a mixed bag of Access 2003, 2007 and 2010. I know we should standardize across the network and that is our goal, but we still need to deal with the current situation.
Response time has become an issue across the network. We've replaced our network switch, and our internet provider, cut out a router and used the one provided by our new ISP instead. That seemed to do the trick, except for:
One particular series of queries and embedded VBA runs one of the major reporting systems on the network. The time it takes to run this procedure has become an issue.
I've determined that all MS Access 2003 workstations run the procedure in 17-18 seconds - and that is acceptable. The MS Access 2007 workstations run the procedure in 12 seconds. BUT - the MS Access 2010 user (just one guy) runs the procedure in 39 seconds. His other MS Access programs run equally slowly in relation to the rest of the network.
I would normally tell the guy to tough it out, but he is the corporate VP and has the attention span of a 3 year old.
Should I convert the whole program front end to 2010 mode for him? What about the back end? It is currently in Access 2000 format.
These mixed marriages are difficult to deal with.
I'm thinking of getting Access 2010 Runtime for all users and have one workstation as a development system - converting the Back End to 2007 format.
Any suggestions/opinions are welcome and would be gratefully received.
Response time has become an issue across the network. We've replaced our network switch, and our internet provider, cut out a router and used the one provided by our new ISP instead. That seemed to do the trick, except for:
One particular series of queries and embedded VBA runs one of the major reporting systems on the network. The time it takes to run this procedure has become an issue.
I've determined that all MS Access 2003 workstations run the procedure in 17-18 seconds - and that is acceptable. The MS Access 2007 workstations run the procedure in 12 seconds. BUT - the MS Access 2010 user (just one guy) runs the procedure in 39 seconds. His other MS Access programs run equally slowly in relation to the rest of the network.
I would normally tell the guy to tough it out, but he is the corporate VP and has the attention span of a 3 year old.
Should I convert the whole program front end to 2010 mode for him? What about the back end? It is currently in Access 2000 format.
These mixed marriages are difficult to deal with.
I'm thinking of getting Access 2010 Runtime for all users and have one workstation as a development system - converting the Back End to 2007 format.
Any suggestions/opinions are welcome and would be gratefully received.