Difference between revisions of "MS Access and MySQL/connecting"
m (fixed partial sentence) |
(→Notes: solved table-locking problem) |
||
| Line 19: | Line 19: | ||
Access also has trouble dealing with AUTOINCREMENT fields (usually used for ID) in the table data viewer. If you create a new field but leave the autonumbered ID field blank, on exiting the field Access will show the record as "''#deleted''". If you close and reopen the table data view, the new data appears. If you enter an ID by hand when you create the record, this problem doesn't happen. | Access also has trouble dealing with AUTOINCREMENT fields (usually used for ID) in the table data viewer. If you create a new field but leave the autonumbered ID field blank, on exiting the field Access will show the record as "''#deleted''". If you close and reopen the table data view, the new data appears. If you enter an ID by hand when you create the record, this problem doesn't happen. | ||
| − | + | ===Problems Solved=== | |
| + | I ran into a problem writing records using [[DAO (Microsoft)|DAO]]. On "Update", an error message stated that another user is trying to write to the same data. The error message: | ||
| − | + | [[Image:MS Access error 3197.png]] | |
| − | [ | + | It turned out that this was because the code was opening a new recordset each time, which apparently I could get away with when the database was local. I also added a timestamp field to the table as recommended [http://forums.mysql.com/read.php?65,43009,44747#msg-44747 here]; it remains to be seen if that was necessary. |
Revision as of 03:02, 1 November 2006
It is possible to use Microsoft Access as a client – or as an intermediary for Visual Basic code – while using MySQL as the database engine. This provides a somewhat less bumpy migration path for VB/VBA applications.
The basic technique is to set up your MySQL server as a data source via ODBC. Then, in MS Access, you link to the tables you want in the ODBC data source.
Instructions
- adding an ODBC data source in Windows 98 (the process should be similar for later versions of Windows)
- connecting to an ODBC data source in MS Access 97 (the process should be similar for later versions of Windows and MS Access)
Notes
ODBC appears to translate data types it doesn't understand into Memo fields. This would be fine, except that you can't sort on Memo fields – so you may have to use types which ODBC can handle better. Fields which can't be sorted on also can't be designated as indexes in the data schema (on MySQL's end), or Access will refuse to import the table.
| MySQL type | MS Access type | Notes |
|---|---|---|
| TINYTEXT | Memo | |
| VARCHAR(255) | Text | field size = 255 |
(I'll add to this table as more examples come up.)
Access also has trouble dealing with AUTOINCREMENT fields (usually used for ID) in the table data viewer. If you create a new field but leave the autonumbered ID field blank, on exiting the field Access will show the record as "#deleted". If you close and reopen the table data view, the new data appears. If you enter an ID by hand when you create the record, this problem doesn't happen.
Problems Solved
I ran into a problem writing records using DAO. On "Update", an error message stated that another user is trying to write to the same data. The error message:
It turned out that this was because the code was opening a new recordset each time, which apparently I could get away with when the database was local. I also added a timestamp field to the table as recommended here; it remains to be seen if that was necessary.