This is the DBConvert for MS Access & PostgreSQL Frequently Asked Questions. If you meet any problem using the application, please read this document before contacting us. We are sure that you will easily find an answer to your question, or your problem resolve here. If not, only after that you should contact us per e-mail esupport@dbconvert.com
Why should I use DBConvert for MS Access & PostgreSQL tool, not other tools? - As well as an ultimate ease of use,this database conversion tool can give you an advantage in speed. Regularly benchmark tests show that DBConvert for MS Access & PostgreSQL product obviously stands out from the crowd of similar data conversion tools with its improved general functionality, high speed of conversion and stability of the software.
Where can I learn more about PostgreSQL and Microsoft Access databases?
PostgreSQL - You should refer to the online manual pages which can be found at
www.postgreql.com/docs
Microsoft Access Database (mdb)
- Beginner's help - Microsoft Access help reference.
- Advanced help - MSDN, (Visual Studio Documentation -> Visual Basic Documentation -> Microsoft DAO 3.60)
I can't connect to PostgreSQL server. How can I solve the problem?
If you are using Virtual Server hosting you probably have no sufficient privileges to create new databases on the target PostgreSQL server. For this case we recommend the following approach:
1. Ask your Virtual Server administrator to create blank database for you
2. Run DBConvert for MS Access & PostgreSQL and select this database as the conversion destination
3. Check option to overwrite existing PostgreSQL database
When you complete these steps, the entire contents of the source MS Access database will be imported into the specified PostgreSQL database.
In case a direct access to your PostgreSQL base is denied, DBConvert for MS Access & PostgreSQL allows you to overcome such restrictions (e.g. you have no sufficient privileges to create new databases on the target PostgreSQL server). You can do it through storing your data in dump file as the best way to present deferred conversion and gain more control over the conversion process. The program fixes the contents of the source database into a local dump file instead of sending it to PostgreSQL server directly. The destination file will consist of PostgreSQL statements to create all tables and to fill them with the data. Using this dump file PostgreSQL server administrator will add data to your PostgreSQL base.
I have an error that selected collating sequence is not supported by the operation system. How can I fix this problem?
One of the following conditions is true:
1. You are trying to open a database or an object in a database that was created in another language edition of Microsoft Access.
2. You are trying to open a database that was created or compacted while the New Database sort Order was set to a value other than General.
To check the settings of the New Database Sort Order, follow these steps:
Open an existing database that was not created or compacted while the Sort Order was set to a value other than General. On the Tools menu, click
Options, and then click the General tab. Make sure that the New Database Sort Order is set to General and then click OK.
If you are receiving the errors and setting the New Database Sort Order back to General does not resolve the problem do: On the Tools menu select Database Utilities, and then click Compact and Repair Database.
Why the date "0000-00-00" in PostgreSQL table was converted into MS Access as "December 30, 1899"?
MS Access has date limits, all PostgreSQL dates less than "January 01, 100", are replaced with date of "December 30, 1899" in MS Access.
When I convert mdb file to PostgreSQL, the program keeps the double quote around the names of the database elements names.How can I remove the double quotes?
In PostgreSQL names (identifiers) are not case-sensitive (i.e. A=a)
In order to keep upper case in your names our program convert the data with double quotes.
To resolve the case "TableName" should be written as “tablename”.
Please, use the option to "Use lowercase" at Customization step(Database Options).
If you check this option all the names of the database elements will be converted in lower case.
For example: “TableName” will be converted into “tablename”.
When converting data from PostgreSQL database to MS Acceess a new database file is created in MS Access 2000 format. How can I convert my database to MS Access97 format?
1 Create a blank database file in MS Access 97 format.
2 Close this blank database.
3 Specify this database as destination database.
After the conversion the database will be available in MS Access 97 format.
Out-of-date Microsoft Jet versions and Microsoft Data Access Components
Some troubles with running the program can be caused by utilizing of the out-of-date Microsoft Jet versions and Microsoft Data Access Components. The latest versions of Microsoft products should be installed in this case. You can download them by clicking at the following links:
Microsoft Jet:
Use Jet40SP8_9xNT.exe to install Jet 4.0 SP8 on computers that are running Windows 95, Windows 98, or Windows NT 4.0.
Use Jet40SP7_WMe.exe to install Jet 4.0 SP7 on computers that run Windows Millennium Edition.
Use WindowsServer2003-KB829558-x86-ENU.exe to install Jet 4.0 SP8 on computers that are running Windows Server 2003.
Use Windows2000-KB829558-x86-ENU.exe to install Jet 4.0 SP8 on computers that are running Windows 2000.
Use WindowsXP-KB829558-x86-ENU.exe to install Jet 4.0 SP8 on computers that are running Windows XP.
Microsoft Data Access Components:
All version Windows (MDAC) 2.8
After conversion date formatting of "mm/dd/yyyy" is replaced with "yyyy-mm-dd 00:00:00". Do you know of a way that I can retain the mm/dd/yyyy format after converting my base to PostgreSQL?
The problem you described is caused by the PostgreSQL server settings configuration. You can use in your queries DateStyle () function to modify date according your requirements. Additional info and documentation about this function you can find in PostgreSQL server Manual
I use converter demo version and get error “Foreign key constraint fails”
Due to trial version limitation (first 10 records from each table) the error “Foreign key constraint failed” may appear. This problem comes up when you copy table records with foreign key references or records protected with other constraint methods maintaining database integrity.
I still have questions/comments about this program - Please, direct them to esupport@dbconvert.com All your feedbacks are highly appreciated.