DBConvert & DBSync for MS SQL & MySQL
DBConvert & DBSync for MS Access & MySQL
DBConvert & DBSync for MS Access & MS SQL
DBForms from MS Access to PHP+MySQL
DBForms from MS Access to ASP.NET + MS SQL
DBConvert for MS Excel & MS SQL/ MySQL
DBConvert & DBSync for MS FoxPro
All «DBConvert» versions convert data from source to destination database. If you don´t have a direct access to the server or have an ftp and PHP access through phpMyAdmin or other tools, «DBConvert» can create «Dump» and «PHP Script» files which contain database info inside and can be executed on the server for putting database there.
Find more details about conversion
«DBSync» versions can both convert and synchronize databases. It strictly needs the direct access to server. «DBSync» provides three types of synchronization:
Our converters guarantee an appropriate running and handling
from command line. You should use the following example for DBConvert for MS Access&MySQL when running the program from the command line:
C:\Program Files\DBConvert\Access2MySQLPro\Access2MySQLPro5_Cons.exe /Session:"Session Name"
Where /Session:"Session name" defines what precreated session should be used This option lets you run converter with the settings which have been stored as a session. All passwords are saved too.
You can automate running synchronization process by using built-in Scheduling stage. It allows executing reoccurrences in a specified time interval. Scheduling process runs automatically in the background mode without any further user intervention.
A batch file is a file that contains a series of commands which the computer executes automatically. Batch files have .bat extension.
Additional information about batch files you can find at http://en.wikipedia.org/wiki/Batch_file or at http://www.computerhope.com/batch.htm#01
You can create .bat files in two ways:
1) Automatically: using Built-in Scheduler that is performed in all DBConvert tools. In this case you don’t need to use shell commands. Our converter does it automatically when you add new task for scheduling. You can read a brief manual at http://dbconvert.com/scheduling_man.php?url=add-new-task
2) Manually: by means of any text editor using command shell processor interface. Please, read more information at http://www.computerhope.com/batch.htm#11
Below is a simple batch file example:
cd "c:\Program Files\DBConvert\Access2MySQLSync\"
@ECHO Run application
DBConvert scheduler's work is fully based on Standard Windows scheduler.
1. Please make sure that you specified your Windows login and password in DBConvert Scheduler settings. Otherwise your task won't be executed.
For this purpose, press "Edit task" option, choose "Settings" tab and fill in the username, password and confirm password fields with the info you use for logon in Windows system. Your password and confirm password must be the same.
Pay attention that DBConvert products use standard Windows scheduler to create tasks for conversion/synchronization. Take a look at the example of .bat file creation:
cd "c:\Program Files\DBConvert\Access2MySQLSync\"
@ECHO Run application
If you have already created sessions you can just specify them in bat file.
Note: Regarding the issue with Standard Windows scheduler MSDN says the following:
"When you use the Scheduled Task Wizard to create a scheduled task on a Microsoft Windows computer, you must be a member of the Administrators group, the Backup Operators group, or the Server Operators group on the local computer.
Additionally, you must type the user name and the password of a user account to schedule the task.When the scheduled task starts, it runs as if it were started by this user. Therefore, the scheduled task runs in the security context of this user account.
If you type the user name and the password of a user account that belongs to a group that has more user rights than the group where you are a member, the task will not run as you expect, because the user name and the password are not configured for the task. However, a user may be able to use the “schtasks” command to schedule a task to run in the security context of a user account that has more user rights, including administrative rights."
2. Except login name and password you should specify "end date" for your task.
For this press "Edit task" option, choose "Triggers" tab and specify the triggers conditions for a task. Click on the "Advanced" button and check "End date" option.
3. Also the reason of such scheduler behavior can be unchecked option in standard Windows Scheduler shown on the screenshot below.
NOTE: If you use Windows Vista or Windows 7 you should disable User Account Control (UAC).
Regarding the problem how to configure MS SQL Express version please thoroughly analyze the manual attached. It is just an example for DBSync Access & MS SQL tool, but the rules for all DBConvert are common for all MS SQL related programs.
It can help you to configure your MS SQL Express server for Windows Authentication in a proper way.
See the manual here.
Please download the manual illustrating several SQL 2008 Express settings that must be preconfigured for successful connection establishing in DBConvert tool.
See the manual here.
Please download the manual illustrating several scenarios when Oracle connection problems appear and how these issues can be resolved.
See the manual here.
You need to review the following MySQL settings:
1. Server timed out and closed the connection.
How to fix: check that wait_timeout variable in your mysqld’s my.cnf configuration file is large enough. On Debian: sudo nano /etc/mysql/my.cnf, set wait_timeout = 600 seconds (you can tweak/decrease this value when error 2006 is gone),then sudo /etc/init.d/mysql restart. I didn’t check, but the default value for wait_timeout might be around 28800 seconds (8 hours).
2. Server dropped an incorrect or too large packet.
If mysqld gets a packet that is too large or incorrect, it assumes that something has gone wrong with the client and closes the connection. You can increase the maximal packet size limit by increasing the value of max_allowed_packet in my.cnf file. On Debian: sudo nano /etc/mysql/my.cnf, set max_allowed_packet = 64M (you can tweak/decrease this value when error 2006 is gone), then sudo /etc/init.d/mysql restart.
Yes, it does!
According to product License the Licensee is eligible for free minor and major upgrades within one year from the date of registration. Then the License may be renewed for additional 1-year period by paying a renewal fee to the Licensor.
That means that you may not have to pay a fee for further updates and stay to use your current software version till the end of times.
Our products completely support Primary keys, Indexes and Foreign keys (relations) conversion and synchronization.
Queries conversion is supported by the current products:
- DBConvert for MS Access & MySQL
- DBConvert for MS Access & MS SQL
- DBConvert for MS Access & PostgreSQL
- DBConvert for MS SQL & MySQL
Our converters support only standard data types. Composite or user specified data types are not supported.
If you need to perform the synchronization, then the structure of synchronized databases should be the identical. Only in this case, the synchronization process will be simple and accurate.
There are many factors that have an influence on synchronization speed.
The most important is an availability of primary keys in synchronizing table, another one is a number of fields and records and the last critical issue that can slow down the speed is a data type.
"Update" synchronization works by comparing record-by-record. And if your record contains, let us assume, 5 empty fields, of course, it will be processed much faster than if your records has binary data. "Insert" and/or "Drop" synchronization options compare Primary Keys' set but not each record.
In this situation, we can recommend one of the following solutions:
Filters can not be used for drop synchronization for the following reason:
Drop synchronization is meant for deleting records in the destination that have been deleted in the source. As filters are applied only for source, we can not use them for the records that do not exist.
You are required to buy only one license per your main machine, even if you need unlimited number of conversions/synchronizations. The product can be installed at any machine that has connects to the servers. In this case, you should use multiple sessions. See the picture bellow.
1 Site Wide License is provided for a user who wants to install one program copy on a production server. This kind of licensing allows unlimited developers at a single physical address.
Premium support is provided to persons who have paid for it and is available as an add-on to a product purchase (“Maintenance” option). It entitles you the premium priority for technical support.
In "Work folder" field, in the settings, you can browse a directory, in which the logs and sessions will be saved.
But as default, a full DBConvert log file is stored at: C:\Program Files\DBConvert\Program name in LOG folder.
Sessions are saved to C:\Program Files\DBConvert\Program name in Program name Sessions folder.
"c:\Program Files\DBConvert\Access2MySQLSync\Access2MySQLSync Sessions"
In case you want to find the modified synchronization log, please follow the link: C:\Program Files\DBConvert\Program name\Program name Diffs
"c:\Program Files\DBConvert\Access2MySQLSync\Access2MySQLSync Diffs"
To store a session you need to have administration rights on the installation folder. Or change the folder for session storage. The new folder should have “Write” permission.
The size of a database you attempt to convert can be limited by DBMS and restrictions related to the data types which are defined in DBMS. Conversion speed directly depends on database size, its structure complexity and hardware set on your PC.
Our products convert such database elements as tables, fields and indexes. If you needn´t convert your whole database there is an option to convert certain table, field or index from a source database. You simply can customize your conversion settings.
Yes. There are two ways of data handling available:
Below the list of supported server types is presented:
Database synchronization is based on the primary keys in table structure. For proper synchronization process your tables should have primary keys, so please make sure whether the primary keys are set in the table.
The comprehensive guide covering SSH options configuration with PuTTY for DBConvert tools is available.
To overcome this problem, please check "Automatic structure update in the session" option at the execution stage. This option enables you to update db structure in the session automatically. Before checking this option, save the current session and when you load this session the next time all new fields and tables will be converted without loss of information.
Please use the following manual for MSSQL Server configuration for clients (machines) connection.
See the manual here.
Usually, when you try to convert large tables we advise the following scenarios:
1. Please upgrade MDAC(Microsoft Data Access Components)
2. Also you can try to increase timeout parameter on MS SQL server as shown on the screenshot attached.
3. Another option to overcome this error to use 'Quantization ' feature in DBSync for that table you receive 'object was open' error for. Usually, error appears on large tables.
To increase conversion speed you must have a unique key. If the unique key points to a single field, the conversion occurs rapidly (1 million records in 5 minutes), if the unique key indicates the number of fields, the conversion takes long time. It can be in 10 times slower.
MySQL error 2003 means server does not have necessary permissions or access rights to the specified directory. Before connecting to MySQL server check your firewall settings or contact your system administrator. Or it may also be you have to reconfigure your MySQL server settings.
This error occurred because of unregistered DBSync for MS Access & MySQL version usage. Foreign key structure can not be built correctly due to 10 records limitation.
MySQL server reports this error when:
- The referenced table is not an InnoDB table
- The referenced column in other table is not unique
- The referenced column in other table has a different type to other id
In MySQL prior to 5.0, this error can also indicate that:
- No index has been defined on the column id
You should customize synchronization properties correctly by checking "Insert sync" and "Update sync" options for all tables. At the same time you need to have, at least, one unique primary key field per table you want to synchronize. Otherwise, synchronization works incorrect or doesn't work at all.
This error occurred because the connection to MySQL Server during query is timed out. Please contact your server administrator for increasing time for queries execution.
Error 3044 is returned by MS Access in case if Access db has linked tables which are not found according to the specified path.
DBConvert and DBSync Access-related products require Microsoft Access to be installed on the machine where Access database file located.
There are 3 ways of connection with MS SQL. You can do it through :
1. - TCP/IP
2. - IPX/SPX
3. - PIPE
Our tool uses TCP/IP protocol for conversion process by default. You should open this protocol through MS SQL Configuration Tools. If you still can not connect to the server check firewall settings or reconfigure your MS SQL server using one of the ways described above. Also make sure that password field is empty if you log in as super administrator.
The general idea of DBForms from MS Access to PHP+MySQL product is conversion of MS Access forms to web page. It may be needed when you want your users have access to data through web resource. Converted forms performed as php files are presented in web browser Exactly the way they were created in MS Access.
Before running DBForms from MS Access to PHP+MySQL you should have the following software installed:
- MySQL server
- Web server (IIS, Apache etc.)
In case you don´t want to adjust settings of MySQL server, PHP and Web server working together we can recommend you to use «3 in 1» package products, such as:
- Denwer and many others.
They require the minimum of user´s participation. After package installation these 3 components work together perfectly.
Note: Pay attention to additional libraries supplied with web server that must be loaded for work with PHP. Please read PHP and Apache help files if you intend to configure them manually.
Our last DBForms from MS Access to PHP+MySQL converter version supports conversion of subforms and tabular controls.
More likely, the problem is masked in unconnected MySQL database with PHP script language. Also you can check folders structure where converted form files must be saved. In case form conversion is committed successfully and the main problem is in uploading php files to local folder or FTP server you can find "Templates" directory. Usually it is placed at "C:\Documents and Settings\User_name\Templates". Here A2WebForms folder must be created. So all php form files can be simply copied from A2WebForm folder to your local folder specified at Upload setting stage.
If you want to update your records in MySQL database you should use our DBForms from MS Access to PHP+MySQL + DBSync for MS Access&MySQL package where DBSync for MS Access&MySQL performs «Update» functionality.
Unfortunately, DBForms doesn't support Access 97 but you can run your database in one of the later Access versions. It will be automatically saved in a new format. Then try to use your database in DBForms as a source.
Please follow the link below to overcome your problem: http://dev.mysql.com/doc/refman/5.1/en/old-client.html
We had faced this problem and figured out where the core is. After queries and forms deletion from MS Access db the information about them is still there, it is not visible in the list of available elements but, be sure, it is left in your db structure. Unfortunately, this is the problem of MS Access only.
As an advice you can create a new db and copy your db elements there.
Before running DBForms from MS Access to .NET+MS SQL you should have the following software installed:
- MS SQL server 2000 and higher versions
- Windows based web server (IIS 6 and higher versions)
- ASP.NET 2.0
In order to increase the speed, you should uncheck "skip empty rows" option at the "Database structure configuration" window.
Such a situation usually happens due to the way the tables(.dbf files) were created. If you want your .dbf tables to be converted easily they must be free, not constrained within a database.
Note: Regarding this problem please check the following details:
- if you choose directory with .dbf files and tables do not appear on Customization stage :
The conversion process will be executed if you moved the destination file to a different folder. You can NOT have the destination file in the folder where you are reading the dbf files from.