When more than the default number of tables are opened, the error message is displayed, the flow stops and rollback is done. There is a default limitation to the number of opened Memory tables. The solution for this case is described below. Sometimes the message appears when working with a memory table (either one created by the engine for its internal usage such as sorting or an application memory tables defined by the programmer). Usually such a message can appear on physical tables and can stem from various reasons (no write permissions, no such location, location inaccessible, etc.). Why is the error message "Failed to open, data source: \m" appearing in the status line and mgerror.log file? Open the project and try running the APG on the data source. If you are trying to create a new data source, you can instruct Magic xpa to create the data source for you by doing the following:Ĭlose the Magic xpa project (but not Magic xpa).įrom Options > Settings > Databases, select the database that you are using in the data source.įrom the Database Properties, go to the SQL tab and check the Check Existence check box. This error means that a table that you are trying to access does not exist. Why I am I getting the "Invalid object name ''" error? The databases are using the correct logical names, which are case sensitive. The translation for the logical names include a trailing backslash (\). The logical names are pointing to the correct directory. To solve this problem, check the logical names. This error means that a physical file you are trying to access does not exist or you do not have the permissions to access it. Why I am I getting the "Failed to open lock file, data source: filename" error? You need to correct your data or cancel your changes by opening the Edit menu and selecting Cancel.
#Unipaas runtime error update#
These errors mean that you tried to create or update a record and this update violates a database constraint, such as a having two records with the same ID (duplicate unique index). Why am I getting the "Duplicate index, data source" or "Constraint failure, data source" error? These exceptions can be trapped by an error event handler in the Magic xpa program. Once Magic xpa no longer checks the index, a duplicate value will cause the database to throw an exception. This change will avoid the index check by the Magic xpa engine (available for ISAM databases only). Uncheck the Check index Database entry property. How can we avoid the status line's "duplicate index" notification and trap the error in an event handler (error handler) when a Duplicate Index error occurs? Check to see if there is an error in the Activity Log. If you are working with deferred transactions, there may have been an error that occurred in a subtask and therefore the entire transaction was not committed to the database. Why when my program is running, why is the data not being saved to the database?
0 kommentar(er)
