Errors

Tip: When you need to contact ProMatrix technical support for assistance with an error, please provide the error information displayed on the Errors form.

Two errors logs are maintained while you work on an application in VPM Enterprise. There is a VPME errors log and an application errors log.

·       VPM Enterprise Errors: If an error occurs while you are in VPM Enterprise, the error information is stored in the VPME error log. You can view the VPME error log on the Errors form reached by selecting the ProMatrix Errors option on the VPME PM-Admin menu. 

·       Application Errors Form: If an error occurs while you are running your application, the error information is stored in your application’s error log. You can view the application’s error log on an Errors form in two places: (1) by selecting the Test Errors option on the VPME Tools - Test menu, or (2) by selecting the Errors option on your application’s Admin menu. 

Tip – Use Errors Form in Application: The Errors form in your application provides more functionality for filtering and ordering errors records. Therefore, we recommend using the Errors form reached from the Admin menu in an application. However, if you only want to see the last application error and you are in VPME, use the Test Errors option on the VPME Tools – Test menu.

Find Errors Filter

When you select the Errors option on your application’s Admin menu, a Find form is displayed that allows you to filter the errors records that will be accessible on the Errors form.

·       Date Range: When the Find form appears, the Date Range is set to the current date. You can enter the range of dates for which you want to view application errors.

·       Users: If you’ve implemented User Access Security in your application, you can view errors for the current user or for all users who have run the application by clicking the option buttons in the Users box.

·       Origins: If the application is sharing its error file with another application, you can view errors for all applications by clicking the All option button in the Origins box. Otherwise, only errors for the current application are accessible.

Errors Form

When you have the Find form set the way you want it, click OK. If more than one errors record matches your Find form filter criteria, the matching records will be displayed in a grid. Select the record you want and click OK. The Errors form will be displayed.

You use the information on the Errors form to resolve errors and debug your application.

You can:

·       Order: Change the order to ascending through the Order button on the Errors form toolbar. You’ll find the toolbar right below the menu bar.

·       Toolbar Controls: You cannot edit or add error records but you can delete them. You should delete the error records before you package your application.

·       Memory: Click the Memory button to see the contents of memory variables and arrays when the error occurred.

·       Status: Click the Status button to see the status of the Visual FoxPro environment when the error occurred.

·       To Clipboard: Click the To Clipboard button to copy the error information displayed on the Errors form to the Windows clipboard.

Tip: You can later paste the error information into a document or email message if you need to communicate the error information to ProMatrix.

The following table explains the fields on the Errors form.

Errors Fields

Contents

User ID

Blank if User Access Security is not on; otherwise, contains ID of the user who experienced the error.

Origin

Contains the 20-character Origin (cOrigin field in SVPMApplicationDefinition.apd) entered on the Environment form for the application that produced the error, or if empty, that application’s 3-character prefix.

Error Number

Visual FoxPro error number.

Date/Time

Date and time the error occurred.

Message

Visual FoxPro error message.

Class/Program

Class contain the method in which the error occurred or the program running when the error occurred.

Method/Procedure

Method in which the error occurred or the procedure in which the error occurred.

Line Number

Number of code line that produced the error.

Code

Code line that produced the error.

Errors Report

The VPM Enterprise and application Report Managers contain an errors report. The errors report prints error records in the errors table. You can select the report’s order, filter and scope.

Errors Table

The errors records are stored in the SDATAErrors.DBF table.

Errors Management

If an application gets a lot of use, the number of records in the errors table can get large very quickly. Periodically, backup the errors table and delete its records.  You can use the Group Delete Toolbar Control on the Errors form or the Zap function in the Data Manager.

More:

Bypassing VPME Error Handling