2 replies
by agoaks Accepted solution
by tony hopkinson Accepted solution
not sure I even would either. Your comment about moving the the database onto the server was moderately surprising as not doing that would make moving the run time massively pointless. Not sure why it's going that much slower on the server though. Have you tried it direct i.e run the access app on the console. ie are the queries taking four times as long or is it taking for times as long to show the results on the client?
Aside from it being a bit too greedy resource wise and getting squeezed by per process quota limits, I can't think of any particular reason why it should n't work. Please bear in mind it's going to be just as flakey multi user wise as it would if you sited the mdb on any accessible drive in your network.
This discussion is closed to new replies.
Trending Networks posts
Sort by Trending