We want to introduce a number of rebranding features included in this release:
* Advances command line processing
* Data filters support
* Drop-synchronization (for synchronizers)
One of the most important features requested by our valued customers is integration of data filters that allow users to specify filtering criteria for conversion. Filters give you more control on data migration process.
Another innovation applied to all conversion tools is advanced command line handling. You can track each program step getting operation status during conversion process in command line mode.
Drop-synchronization is integrated in DBSync series allowing users to delete records from destination database if these records are not presented (were deleted) in source.
You are welcome to try our rebranded products at:
We hope that you will be pleased to work with our DBConvert products which have new looks, names and better conversion performance.
DBForms from MS Access to PHP [HTML_REMOVED] PostgreSQL is an efficient converter designed in addition to DBForms from MS Access to PHP [HTML_REMOVED] MySQL for migration MS Access forms to web page on the base of PostgreSQL server. Our conversion solution performs accurate and rapid MS Access database replication to PostgreSQL database with generating php files for presentation Access forms as web pages.
You can test DBForms from MS Access to PHP [HTML_REMOVED] PostgreSQL before buying. Please download trial version at:
DBConvert for MS Access and MS FoxPro is a tool developed for conversion MS Access databases to MS FoxPro and vice versa. It is easy, rapid and effective.
DBSync for MS Access and MS FoxPro is designed for bi-directional synchronization of MS Access and MS FoxPro databases. Add, update and drop synchronization will help you to keep your databases up-to-date.
Feel free to contact us via e-mail firstname.lastname@example.org to share your opinion about our new rebranded tools. Your comments and suggestions are welcome.
This post has been migrated from a previous version of the PostgreSQL website. We apologise for any formatting issues caused by the migration.