Troubleshooting

While working with Access-to-MySQL Pro wizard you may encounter unexpected behavior or result. Use the following information to solve some common problems and get the result you want. This summary is organized as a list of problem-resolution pairs. Each problem description starts with "P:" and each resolution - with "R:".

P: Error message "The program does not support authentication protocol requested by server..."
R: MySQL 4.1.0 uses the authentication protocol based on a password hashing algorithm that is incompatible with that used by Access-to-MySQL Pro. You can use OLD_PASSWORD function to make the certain account compatible with Access-to-MySQL Pro. Login to MySQL server with administrator privileges and run the following queries:

mysql> USE mysql;
mysql> UPDATE user SET Password = OLD_PASSWORD('some_pass')
-> WHERE Host = 'some_host' AND User = 'some_user';
mysql> FLUSH PRIVILEGES;

Of course, you should place actual values instead of 'some_pass', 'some_host' and 'some_user'. Now you can use 'some_user' account with Access-to-MySQL Pro.

P: Error message "Can't connect to MySQL server on <host name or IP>".
R: Make sure MySQL server is launched on the target machine. Also please check the port number field to verify that you have specified the correct number.

P: Error message "Access denied for user: <user-name>"
R: You will not be able to connect to the target MySQL server until you have the appropriate permissions. Ask your MySQL server administrator to give you sufficient permissions to create new databases on the target MySQL server. See VServer User Notes article for related information.

P: Error message "Cannot extract relationships information..."
R: You need read-permissions on system tables to be able to extract relationships information. Follow these easy steps:
1. open the database in Microsoft Access
2. go to 'Tools'>'Options' menu
3. in the appeared dialog box select "View" tab and activate "System Objects" check box
4. push "Apply" button and close the dialog
5. select "MSysRelationships" table and go to 'Tools'>'Security'>'User and Group Permissions'
6. in the appeared dialog box select "Read Data" checkbox
7. push "Apply" button and close the dialog
8. close Microsoft Access

P: In the resulting MySQL database all MS Access hyperlink fields appear as strings that look like some_text#some_other_text#.
R: MySQL has no data type similar to hyperlink. That's why the only way to save the entire information is to import it into plain text. Access-to-MySQL Pro converts each hyperlink field into MySQL TEXT field formatted as <URL name>#<URL address>#.

P: The program converted all database fields fine but where are my MS Access forms?
R: Access-to-MySQL Pro doesn't convert MS Access forms because MySQL doesn't support forms.

P: The program converts some of MS Access date fields into MySQL CHAR(19) data type.
R: Unlike MySQL, MS Access has no separated types DATE, TIME and DATETIME. Access-to-MySQL Pro tries to map date columns properly using the content analysis. When it is impossible to perform unambiguous conversion (e.g. column contains pure dates and pure time values), the program converts MS Access date fields into their string representation. This approach preserves ordering relationship inside date/time column, and even you can use the same MySQL queries as if it was a date/time field.

P: Some indexes are missing in the resulting MySQL database.
R: It means that duplicate field values being used for an unique index were found in the source database. MySQL applies more strict limitations on fields including in unique indexes than MS Access. The only way to safely export all MS Access records in the destination database is to remove conflicting indexes.

P: Some table names and/or field names in the resulting MySQL database are different from the original.
R: MS Access and MySQL accept different sets of characters for table names and field names. When Access-to-MySQL Pro converts a name containing prohibited characters it replaces them with '_' in the destination database.

P: When leaving the third wizard screen I can see the following error message: Access denied for user: '<user-name>' to database '<database>'
R: If the destination database already exists, you should have necessary privileges to add/remove tables. If the destination database doesn't exist, you should have sufficient privileges to create new databases on the target MySQL server. See VServer User Notes article for related information.

P: The program does not convert default values for MS Access MEMO fields.
R: Access-to-MySQL Pro converts MEMO fields into MySQL TEXT type as the most appropriate on a range of acceptable values. TEXT and BLOB fields cannot have default values.

P: Some empty fields have appeared in the resulting MySQL database with nonempty values.
R: Unlike MySQL, MS Access allows the fields declared as NOT NULL to have empty value. To prevent conflicts during the conversion process Access-to-MySQL Pro assigns the default value to each of those fields.

If you came across some other kind of problem while using Access-to-MySQL Pro, please contact our support department at support@convert-in.com