Database in LAN vs mySQL server

[calvinle]

Hi,

I have created an access database with linked table to a backend database using DAO code. We are in discussion to move the backend table in the LAN to mySQL server, so I am wondering how thag works? Will my DAO code will still work? or I have to modify all my DAO to ADO?

Because we are accumulating a lot of data and the LAN is getting slow using the access database. What are the main changes if they decide to move to mySQL server?

Thanks

 

[CJ_London]

if your LAN is slow, moving to MySQL server will not necessarily solve the problem since you will still be transferring data across the LAN.

see post #2 of this link where the same question is asked

http://www.accessforums.net/showthread.php?t=62876&p=337384#post337384

Unless those questions have already been resolved, you are unlikely to see an improvement in performance.

You might also want to consider investing in terminal server or citrix - users will then see performance very close to having the backend on their local drive since the only thing going across the LAN is screen refreshes one way and keyboard/mouse events the other

 

[stopher]

Do some research/tests on passthrough queries. If you run a query using the Access database engine then the engine pulls all the data from the source tables over the network and then processes the query locally. With a passthrough query, the query is passed to the server and the server processes the query and returns only the returns (or processes the results locally). This can be a huge gain if you are running a filtered/aggregated query for a report or maybe a form where you only need to see one record. Of course your server needs to be capable of

I understand ADO particularly is passthough native so you may want to look at optimising ADO. But I have little knowledge of this.

 

[calvinle]

Do some research/tests on passthrough queries. If you run a query using the Access database engine then the engine pulls all the data from the source tables over the network and then processes the query locally. With a passthrough query, the query is passed to the server and the server processes the query and returns only the returns (or processes the results locally). This can be a huge gain if you are running a filtered/aggregated query for a report or maybe a form where you only need to see one record. Of course your server needs to be capable of

I understand ADO particularly is passthough native so you may want to look at optimising ADO. But I have little knowledge of this.

I have though about this but the database is used by multi user, 50+.
It might have conflict to save the data back to the LAN by multiple users.