ConversionTool software
have been tested by alienpicks.com team against viruses,
spyware, adware and was founded to be 100% clean.
We will recheck this software periodically to assure users that it remain clean.
|
ConversionTool 4.2.2 Antivirus Report
Archive: DBX%20Conv.zip
inflating: setup.exe
inflating: SETUP.LST
inflating: ConVersionTool.CAB
Scanning SETUP.LST
SETUP.LST: OK
Scanning setup.exe
setup.exe: OK
Scanning ConVersionTool.CAB
ConVersionTool.CAB: OK
Scanning DBX%20Conv.zip
DBX%20Conv.zip: OK
----------- SCAN SUMMARY -----------
Scanned directories: 1
Scanned files: 4
Infected files: 0
Data scanned: 6.07 MB
Time: 3.422 sec (0 m 3 s)
|
|
|
|
Get The Code for ConversionTool 4.2.2 Antivirus Report:
|
|
|
|
You are welcome to display a text or a graphic link on your website and link-it
to this antivirus report page. Below are the codes: |
|
|
Graphic link:
|
Example:
|
|
Text link:
|
Example:
ConversionTool Antivirus report
|
|
|
|
|
ConversionTool 4.2.2 Description:
Our tool reengineers BTrieve databases and converts comprehensively a MS Access database into a SQL Server database, unlike the Microsoft’s UpSize Wizard preserving all table structure details, and supports the conversion of the views and procedures. Moreover, the tool supports solution of structural problems between Access and SQL Server like making the implicit behavior of boolean fields in MS Access explicit in SQL Server by setting the default to FALSE and making the field required. We understand that not everything can be converted automatically. First of all, there is the complexity of translating database functions into their SQL Server counterparts. Add the problem of user-defined functions (in VBA), where VBA code would have to be translated into SQL Server syntax elements in a user-defined function. But there are also decisions to make regarding changes in the client application. Take a view for example with two fields of two different tables with the same name, which is possible in Access but not in SQL Server. MS Access would expose field names like [<table name>.<field name>] in order to make the name unique, but since SQL Server does not allow such a syntax, the fields would need to get another name; with all consequences for client applications using this view. To deal with all these problems, our tool converts everything it can automatically. All remaining items are identified, the problem is shown clearly to the user, and an interactive mechanism is provided. If, for example, a record could not be inserted due to a constraint violation (a wrongfully inserted date like 1/1/199), this insert instruction is logged in a separate error log, and can be edited and executed. When a referential constraint fails, our tool creates automatically a view in both the source and target database, containing the foreign key records, which don’t match a primary key. Our tool is also prepared to convert from or to other database systems. Starting with version 2.1, any source databases can be converted to SQL Server.
|
Download link:  |