MS Access as a DB

NZ_Kiwis

Okay, I've got a program on my machine and I want it to send stuff to my online DB (Remote MySQL) this can not be done other than web services which is to hard to learn so I want a quick fix for now and I have one big question

Can i connect to a remote access .mdb??

I'm on a Unix system with PHP 5

I think intend to synchronize the two DB with a PHP script.

bpat1434

PHP Manual » Database FAQ wrote:
61.2. Can I access Microsoft Access databases?
[indent]Yes. You already have all the tools you need if you are running entirely under Windows 9x/Me, or NT/2000, where you can use ODBC and Microsoft's ODBC drivers for Microsoft Access databases.

If you are running PHP on a Unix box and want to talk to MS Access on a Windows box you will need Unix ODBC drivers. » OpenLink Software has Unix-based ODBC drivers that can do this.

Another alternative is to use an SQL server that has Windows ODBC drivers and use that to store the data, which you can then access from Microsoft Access (using ODBC) and PHP (using the built in drivers), or to use an intermediary file format that Access and PHP both understand, such as flat files or dBase databases. On this point Tim Hayes from OpenLink software writes:

[indent]Using another database as an intermediary is not a good idea, when you can use ODBC from PHP straight to your database - i.e. with OpenLink's drivers. If you do need to use an intermediary file format, OpenLink have now released Virtuoso (a virtual database engine) for NT, Linux and other Unix platforms. Please visit our » website for a free download.[/indent]

One option that has proved successful is to use MySQL and its MyODBC drivers on Windows and synchronizing the databases. Steve Lawrence writes:

Install MySQL on your platform according to instructions with MySQL. Latest available from » http://www.mysql.com/ No special configuration required except when you set up a database, and configure the user account, you should put % in the host field, or the host name of the Windows computer you wish to access MySQL with. Make a note of your server name, username, and password.

Download the MyODBC for Windows driver from the MySQL site. Install it on your Windows machine. You can test the operation with the utilities included with this program.

Create a user or system dsn in your ODBC administrator, located in the control panel. Make up a dsn name, enter your hostname, user name, password, port, etc for you MySQL database configured in step 1.

Install Access with a full install, this makes sure you get the proper add-ins... at the least you will need ODBC support and the linked table manager.

Now the fun part! Create a new access database. In the table window right click and select Link Tables, or under the file menu option, select Get External Data and then Link Tables. When the file browser box comes up, select files of type: ODBC. Select System dsn and the name of your dsn created in step 3. Select the table to link, press OK, and presto! You can now open the table and add/delete/edit data on your MySQL server! You can also build queries, import/export tables to MySQL, build forms and reports, etc.

Tips and Tricks:

You can construct your tables in Access and export them to MySQL, then link them back in. That makes table creation quick.

When creating tables in Access, you must have a primary key defined in order to have write access to the table in access. Make sure you create a primary key in MySQL before linking in access

If you change a table in MySQL, you have to re-link it in Access. Go to tools>add-ins>linked table manager, cruise to your ODBC DSN, and select the table to re-link from there. you can also move your dsn source around there, just hit the always prompt for new location checkbox before pressing OK.
[/indent]

»» Original Text

Hope that answers your question 🙂

MarkR

What you're proposing doing sounds iffy at best.

It would be better to use MSAccess as a front end to the mysql, if there is a genuine requirement to use it at all.

MSAccess (or specifically JET db engine) is unsuitable for use in a production environment, I've seen loads of people try to use it and always succeed in getting the DB corrupted or having their service fail in some way.

Mark