Features new in v4.0
Completely rewritten user interface
Do you like the simplicity of the new Office 2007?
We believe database conversion should be as simple as it gets. To simplify the process for you, we have completely rewritten Full Convert user interface.
Menu and toolbars are replaced by a ribbon, so you don't need to dig through menus or wonder if an action will cause data modification.
We have separated available actions in three tabs - Home, Advanced and Analyze. Most user's will do everything they need using Home tab only. However, for maximum customization and analysis of the conversion, feel free to explore all the options at your fingertips.
Did we mention that it also looks much better now? :)
Full Unicode support
This is a much requested feature and was the main cause of the long development of v4.0.
You can now be certain that all your fancy characters will remain the same at the target after the conversion. Chinese, Japanese, Hebrew, Arabic, Slavic, German umlauts etc. won't be lost and you won't need to perform character set conversion if your databases are properly configured.
Microsoft Excel is now supported as a target
Another much requested feature.
Although we initially added support to export to Excel documents into our data grid, we realized this is going to be cumbersome for hundreds of tables.
Excel is now a first-class target. You can even choose whether you want to convert each source table as a different Excel file, or all tables into a single document, easier to send to the colleagues.
If you choose to output a single Excel document for all tables (each table will then be represented as a worksheet inside Excel document), just specify its filename. If the file doesn't exist, Full Convert will create it for you.
If you choose to output a separate Excel document for every source table, you need only to specify output folder. Each table will have its final Excel document.
You can even explore the resulting Excel documents as a tables right in the Full Convert data grid!
User SQL scripts can be triggered before and after conversion
As much as we are striving to turbocharge the rich customization built into our application, some things can't be added as they would inevitably complicate the user interface for 99.9% of the users who don't need the certain feature.
For all the power-users who need this, we have built the ability to load, write and execture custom user SQL script before and after the conversion.
You can:
1) Write the color-coded SQL script right in our own editor
2) Specify the SQL file to be loaded and executed
3) Specify the ZIP file to be loaded, unpacked and have its contents executed
Of course, we think it's pretty that you can even specify the wildcard file mask of the items inside a ZIP archive that need to be executed.
In-place data editing
Sometimes the data you have in your source database isn't tidied up. Maybe the database didn't have all the checks implemented, or it is an old non-relational database where certain checks couldn't be enforced easily.
Whatever the reason, many users need to fix the data here and there after the conversion. If you needed to fire up your SQL editor to do it, you know that it isn't really a greatest convenience for the job.
For easy making of many small changes, you can now click the button in the data toolbar to enable data editing. Editing is disabled by default, so you can't inadvertently mess up the data.
When you are finished with editing, you can click 'Post' button to save the canges, or 'Cancel' to, well, cancel.
Auto-discovering your source database
Some of our users are incredibly technically advanced. Most aren't.
All is well if you have your databases properly setup and know what to do with the files you got to convert - but we know from our support calls that many users struggle.
Maybe you got a bunch of .MDB files and are asked to convert them to Excel. Or are they GDB files? IB? DBF? DB?
OK, let's see if we can simplify your job - from now on, for a file-based databases, just navigate to the folder containing your source files and Full Convert will analyze them and correctly set up your source database parameters.
Now, all you need to do is press 'Next'.
Improved error reporting
We support 14 databases. Yes, fourteen!
Each and every of those has its own error messages, inevitably different from others and typically not helpful at all for anyone except database experts.
We have taken extra effort to help you out. Full Convert will now intercept the exception when it occurs, analyze the error and provide a helpful tip for the common issues. We will expand the errors handled in our upcoming versions.
And if you have no idea what to do - or you believe the error is in fact a bug in our application - just click the 'Report to support team' button and we will get a technical information about the error and a screenshot. If you are a licensed user, we will even be able to contact you immediately and solve your problem.
Don't know what to do when you get errors? We can help you out.
Another time saver when you start to get errors in conversion.
Sending error log to our Support Team has never been easier. We have added a direct link to immediately send the errors to Full Convert support.
This is just one of the many features built into the Full Convert 4 that is designed to make your experience using our application as pleasant as possible.
See complete version history
See all features
