ConversionTool 4.2.2 details
SPONSORED LINKS
ConversionTool 4.2.2 screenshot and details:
Rating: 3.5 Votes: 0
Company: BI Garant BV
Info url: http://www.keper.com/dbexplorer/conversiontool/index.html
Release date: 2005-08-25
Last update: 2008-03-06
Platform: Win95,Win98,WinME,WinXP,Windows2000
Language: English
File size: 3 KB
System Requirements: MDAC 2.8, JET Comp 4.0
License: Shareware
Price:299 $
ConversionTool 4.2.2 Publisher Review:
.
Rating: 3.5 Votes: 0
Company: BI Garant BV
Info url: http://www.keper.com/dbexplorer/conversiontool/index.html
Release date: 2005-08-25
Last update: 2008-03-06
Platform: Win95,Win98,WinME,WinXP,Windows2000
Language: English
File size: 3 KB
System Requirements: MDAC 2.8, JET Comp 4.0
License: Shareware
Price:299 $
ConversionTool 4.2.2 Publisher Review:
Tool reengineers BTrieve databases and converts comprehensively Access databases into SQL Server preserving all table structure details, and supports the conversion of the views and procedures. Moreover, the tool supports solution of problems.
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 [