hello, I'm pretty good with excel vba but have limited knowledge with Access. The developer who coded this is busy with other projects. From time to time I've found a bug or something small that needed to be changed and mudled my way through the code and have fixed it, but again my access knowledge is very limited.
This access is split front end/back end. On the back end are numerous databases for individual offices stored on a remote server and what is installed for the end-user is just the front-end and it links to their appropirate database upon logging in.
There is this daily check that needs to be run once a day when they log in. On access 2003 (and 2000) for the largest office it takes about 40 seconds. However in access 2010 it's taking about 5 minutes. I still have 2003 so it's still fast for me but I have access to a laptop now and I as well am experiencing the 5 minute run-time. On a hunch, I copied the backend mdb file to my local drive and linked to that. It then ran in about 40 seconds.
So in 2003: local or remote same run-time.
2010 local is fine, remote run-time takes a nose dive.
It doesn't seem to be anything wrong with how the network share is mapped in 2010 as I have written a few excel utilities that query all the databases for reports and they run in the same time in excel 2003 vs 2010, so it seems to be access specific.
Again, I know very little about access, is there some general things I could look at that would explain the above?
It seems the front-end is slower all around in 2010 and not just in this daily check, it's just most apparent when this is running. I'm hoping there's something basic to check on why something would be slower remotely vs a local database in 2010.
This access is split front end/back end. On the back end are numerous databases for individual offices stored on a remote server and what is installed for the end-user is just the front-end and it links to their appropirate database upon logging in.
There is this daily check that needs to be run once a day when they log in. On access 2003 (and 2000) for the largest office it takes about 40 seconds. However in access 2010 it's taking about 5 minutes. I still have 2003 so it's still fast for me but I have access to a laptop now and I as well am experiencing the 5 minute run-time. On a hunch, I copied the backend mdb file to my local drive and linked to that. It then ran in about 40 seconds.
So in 2003: local or remote same run-time.
2010 local is fine, remote run-time takes a nose dive.
It doesn't seem to be anything wrong with how the network share is mapped in 2010 as I have written a few excel utilities that query all the databases for reports and they run in the same time in excel 2003 vs 2010, so it seems to be access specific.
Again, I know very little about access, is there some general things I could look at that would explain the above?
It seems the front-end is slower all around in 2010 and not just in this daily check, it's just most apparent when this is running. I'm hoping there's something basic to check on why something would be slower remotely vs a local database in 2010.