Error when Running Activity Report through ODBC
RecTrac 3.1.10.12.01
Table of Contents
Problem
When running an Activity Report through ODBC, we are receiving an "ARSection has exceeded value" message. We can run the report successfully when running it through RecTrac, but running it through ODBC produces the error. This issue appears to be related to the SQL Width of that field.
Error Message
"ARSection has exceeded value"
Solution
You can implement several steps within your Database Startup Parameters (localhost:9094). To do this, you will need access to your RecTrac database server. If hosted, contact hostedservices@vermontsystems.com with the error message.
- Under the SQL Configuration, called "SQL Truncate Too Large": Within this field, set it to "output" to truncate data that is larger than the current SQL width and will no longer display an error / stop the export. If exporting the information into Excel, a message will display, notifying the customer that data has been truncated.
- Under General (just above the SAL Configuration): Under the "Other Arguments" field, set SQLWidthUpdate to ON to automatically adjust the SQL width of field(s) exported when the SQL width is too small. This process is completed automatically after the data fetch is completed.
So, before setting these values, you are receiving the "ARSection has exceeded value" message. You followed the above steps and run the report. You'll notice the first time that some data was truncated as well as a warning that some of it has been truncated. Wait a few seconds and run the report again. This time, no warning will display at the bottom of the report and all data fields should be complete. While the customer needs to be aware both of the Truncation warnings and needing to run the export again, the widths should adjust automatically.
Note:
You cannot set the the SQLWidthUpdate (Step 2) to ON and set the SQLTruncateTooLarge (Step1) to OFF. If you try this, the SQLTruncateTooLarge will automatically set to OUTPUT. If a customer implements these changes, they need to be mindful / look for truncated information. If they find it, they need to wait a minute and re-run the report to produce a copy of the report without truncated information.
Steps For Solution
- Log onto localhost:9094 on the RecTrac database server, OpenEdge Explorer
- Credentials (unless changed) are admin|admin).
- Select your dbname: LIVE and click on its name to bring up its settings.
- Select your Configuration button (on the left hand side of the screen).
- Underneath your EDIT button is a "configuration.live.defaultconfiguration " Link.
- On the left-hand side of the screen, note a list of options, and click SQL Configuration and the EDIT button on the screen's top left.
- Change the value of the SQL Truncate Too Large to OUTPUT .
- Click Save.
- On the left-hand side of the screen, click the General button and the EDIT button to update.
- To update, under the "Other Arguments" field, add the following -SQLWidthUpdate ON.
- Click Save.
- Return to your Resources screen within OpenEdge.
- Stop all AppServer / WebSpeed Brokers.
- Stop the DB that was just updated.
- Then Start this DB.
- Restart your Appserver/WebSpeed brokers.
- Run your ODBC report.
The first ODBC Export should include a message about truncation / you should see truncated values. Run the same ODBC Export again. You should see the corrected values.
Note:
VS will support establishing an Open Database Connectivity (ODBC) connection in environments where allowed (such as VS Premium Cloud Hosting). The database schema can be printed by running the RecTrac Dictionary Listing report from within the RecTrac application. Current entity relationship diagrams are also available (can be accessed via the VS FTP site). No other ODBC support services will be provided by VS, such as but not limited to development assistance and development troubleshooting.