MS Access to PostgreSQL Troubleshooting |
| [MS Access to PostgreSQL Converter] [Tutorial] |
While working with MS Access to PostgreSQL converter 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 "Cannot recognize MS Access
database format"
R: The first reason of this error is that soure file is not a valid
MS Access database. The second reason could be missing appropriate
Microsoft Data Access (DAO) libraries on the system to read the database.
In this situation it is recommended to install Microsoft Access 2010
Runtime as it contains correct version of DAO libraries:
http://www.microsoft.com/en-us/download/details.aspx?id=10910
NOTE: it must be 32-bit installation pack, even if your system is
64-bit. If the error persists, please contact Intelligent Converters support
service at service@convert-in.com
Go to top
P: In the resulting PostgreSQL database all MS Access hyperlink fields appear
as strings that look like some_text#some_other_text#.
R: PostgreSQL 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. MS Access to PostgreSQL
converter translates each hyperlink field into PostgreSQL TEXT field formatted as <URL
name>#<URL address>#.
Go to top
P: Error message "The specified record violates the integrity
constraints..."
R: This error means that an attempt has been made to insert a record with a
duplicate unique key. When migrating MS Access data into a new PostgreSQL database,
you can either edit source database in order to resolve the conflict manually
or restart the program with "Skip converting indexes" checkbox
selected. When appending MS Access data to an existing PostgreSQL database, you
should remove the conflicting unique index in the destination PostgreSQL database.
Go to top
P: The program does not convert default values for MS Access MEMO
fields.
R: MS Access to PostgreSQL converter translates MEMO fields into PostgreSQL TEXT
type as the most appropriate on a range of acceptable values. TEXT and BLOB fields
cannot have default values.
Go to top
P: Foreign key are missing in PostgreSQL database created
by demo version of MS Access to PostgreSQL converter.
R: Demo version of MS Access to PostgreSQL converter does not porcess foreign key
constraints. This limitation will not appear in full version of the product.
Go to top
P: Error message "CREATE DATABASE permission denied
in database 'master'"
R: This error means that you do not have sufficient permissions to create
databases on destination PostgreSQL server. To fix it you need to login with
administrator's privileges and run the following statement:
GRANT CREATE DATABASE TO <your user name>
If you cannot login with administrator's privileges, ask your database
administrator to do this for you.
Go to top
P: Some empty fields have appeared in the resulting
PostgreSQL database with nonempty values.
R: Unlike PostgreSQL, MS Access allows the fields declared as NOT NULL to have empty
value. To prevent conflicts during the conversion process, MS Access to PostgreSQL
converter assigns the default value to each of those fields.
Go to top
P: Demo version of MS Access to PostgreSQL converter
writes only 50 records per table in the target database.
R: This is limitation of demo version, it will not appear in full version
of MS Access to PostgreSQL converter.
Go to top
P: I cannot uninstall MS Access to PostgreSQL converter.
R: If you need to remove MS Access to PostgreSQL converter from your
computer, you can use "Add or Remove Programs" option in the
Windows Control Panel.
If you came across some other kind of problem while using MS Access to PostgreSQL converter, please contact our support department.