| Severity | Message Type | Message text | Description |
|---|
| Information | Template | Get the template file... | The process is loading your template file |
| Information | Variables | Update with User Variables... | The process is replacing user variables within your template file |
| Information | Output | Open the output... | The process is opening a file to write the generated file to. |
| Information | Data | Processing Data... | The data is being retreived and formatted into your template. While this happens a series of periods ('.') will be displayed, mainly to help identify that data is being retreived. |
| Information | Done | Completed !!! | Good news, the process completed ok. |
| Error | Output File Open | Text will vary | While opening the file for output the program was unable to complete the action. The text will describe the problem. |
| Error | Output File Write | Text will vary | While writing the output file the program was unable to complete the action. The text will describe the problem. |
| Error | Block Process | Bad Block Process | This message usually will appear in conjunction with other messages. It simply indicates that a problem occured while processing a block of template detail. |
| Error | Template Parse | Out of Memory | The system ran out of memory while parsing your template. Either shut down some other processes or increase the memory available. This program does not use alot of memory, so you should investigate what process is using it up. |
| Error | Template Parse | Too many nested Details | The template parser of this version has a built in limit of 20 nested detail blocks. This means that a template may contain up to 20 Begin and End Detail statements at each level of nesting. This restriction should not effect most user templates, however it should be addressed in a subsequent version |
| Error | Template Parse | No detail end mark found | A matching DETAIL END marker was not found for one of your DETAIL START marks. |
| Error | Template Parse | No SQL Block Found | A DETAIL START mark was not immediately followed by a SQL statement. |
| Error | Template Open | Text will vary | While opening the template file for reading the program was unable to complete the action. The text will describe the problem. |
| Error | Template Read | Text will vary | While reading the template file the program was unable to complete the action. The text will describe the problem. |
| Error | Template Size | Maximum template size exceeded | In the current version a template file may be no larger than 32KB. If your template exceeds this size you may want to consider splitting it into smaller files. In most cases a file this large would be a performance consideration on the Internet. Please note that there is no set limit to the size of your generated file, only to the size of the template itself. |
| Error | ODBC | Error locking memory | This error indicates a serious memory problem occured. |
| Error | ODBC | Error on Connect | This error will be followed by further explaination. Most often there is a problem with the configuration of your Datasource or your ID amd Password. |
| Error | ODBC | Error Allocating Connection | This is an unusual error. Check your memory is not too low. The error should be followed by further useful messages. |
| Error (Non-Fatal) | ODBC | Error getting column Name, will continue | This error indicates that the program was unable to get at least one column name. The generation will continue, but no name substitution will be performed on the column in issue. The column number will be displayed on the next line. |
| Error | ODBC | Error Allocating Workspace | Check your memory is is too low. |
| Error | ODBC | Error Binding | This error will be followed by an explanatory message. |
| Error | ODBC | Error Getting column count | There was an error determining the number of columns in the result. This error will be followed by an explanatory message. |
| Error | ODBC | Error executing statement | An error occured executing a statement. Usually there is a syntax issue with the SQL statement. This error will be followed by an explanatory message. |
| Error | ODBC | Error preparing statement | An error occured preparing a statement for execution. Usually there is a syntax issue with the SQL statement. This error will be followed by an explanatory message. |
| Error | ODBC | Error Allocating statement | This is an unusual error. Check your memory is not too low. The error should be followed by further useful messages. |
| Error (Non-Fatal) | ODBC | Error on Disconnect | The process had an error while disconnecting. The error should be preceeded by further useful messages. |
| Error (Non-Fatal) | ODBC | Error on Free Connect | The process had an error while freeing the connection. The error should be preceeded by further useful messages. |
| Error (Non-Fatal) | ODBC | Fetch Message | This error will be followed by an explanatory message. |
| Error | ODBC | Error Allocating Environment | The process had an error while allocating the database environment. Usually this error is related to a memory usage issue. The error should be followed by further useful messages. |
| Error (Non-Fatal) | ODBC | Error on Free Environment | The process had an error while freeing the database environment. Usually this error is related to a memory usage issue. The error should be preceeded by further useful messages. |
| Error (Non-Fatal) | Format Numbers | Formatting error; Format[nnnn], Data [xxxx] | An error occured while processing the format of the specified data. Check that data and format are correct. |
