Besides database and application conversion, Ispirer Toolkit performs comprehensive automatic conversion of embedded SQL statements and database APIs in different applications. With Ispirer Toolkit there is no need to extract SQL statements from application code and convert them separately. The tool completes the entire migration process internally. Ispirer offers its Toolkit and Services for the following programming languages: Delphi, PowerBuilder, COBOL, C/C++, Java, C#, VB.NET, VB and others.

The output is a file(s) with the same extension as before the conversion. Only embedded sql will be converted inside the file. Reports are also generated, by which you can understand whether the file was converted successfully.

• Parser Error

After the conversion process, you may see that some objects or scripts were not converted due to parser errors. It means that the conversion tool was unable to analyze the code of the object or file. In other words, some unknown statements or constructions were found inside the script that we are trying to convert. How to Solve Parser Errors The good news is that these types of errors are very easy to fix and don't require any complicated steps or settings from your side. All you need to do is simply send the code of failed scripts to our support team at support@ispirer.com. And we will extend the parser technology based on the constructions of your code for free. In a couple of days we will provide you with an extended version of the toolkit. Therefore, you can continue to use the migration tool. How to Find Parser Errors in Reports Parser errors may occur during the conversion. For the convenience of viewing error messages, Ispirer Toolkit provides the opportunity to view a full report with the results of the conversion. You can also view error messages in the sqlways.log file located in the export directory.

To open the report, on the Completing page, click on the Review Full Report button.

On the page that opens, you can see information about scripts and errors.

You can click on a file extension and go to the list of all files with that extension with information about whether they were converted successfully or there was an issue during conversion, including parser errors.

To resolve the error, please send the source code of the file(s) or statement in which the error occurred to [email protected]. We will analyze the code and prepare a version of Ispirer Toolkit that will parse the source code.

• Warning that the embedded sql was not found

The warning “Embedded sql was not found” occurs if the embedded sql was not found within the application code or if the tool could not recognize it. In this case please contact [email protected].

If you have any questions or difficulties, please contact us at support@ispirer.com.