[pervasive][odbc client interface] Numeric value out of range. (#0) - MS Access and Sage 50
[pervasive][odbc client interface] Numeric value out of range. (#0) - MS Access and Sage 50
(OP)
We're trying to do some custom reporting off of Sage 50 MRP software. We're using MS Access as the custom tool to write queries, run reports, process data, etc.
We are able to link to several Pervasive tables for our needs. 5 of the 6 don't cause us any headache.
In trying to pull the linked Pervasive table "JrnlRow" to a local Access database, we get the error message in the subject line:
[pervasive][odbc client interface] Numeric value out range. (#0)
This is happening very specifically on the column PostOrder in the table JrnlRow. When we leave that column out, we can get data copied over.
In sorting on that column, we found that there is a constantly varying number of records with have the value #NAME across all fields. I was pretty sure THIS is what is causing the problem, but there are other fields that we are also pulling that are not blowing up due to having those values. So, I can't be sure. However, I believe PostOrder is a foreign key field.
Does anyone have any insight into this? What we can do to fix it?
We are able to link to several Pervasive tables for our needs. 5 of the 6 don't cause us any headache.
In trying to pull the linked Pervasive table "JrnlRow" to a local Access database, we get the error message in the subject line:
[pervasive][odbc client interface] Numeric value out range. (#0)
This is happening very specifically on the column PostOrder in the table JrnlRow. When we leave that column out, we can get data copied over.
In sorting on that column, we found that there is a constantly varying number of records with have the value #NAME across all fields. I was pretty sure THIS is what is causing the problem, but there are other fields that we are also pulling that are not blowing up due to having those values. So, I can't be sure. However, I believe PostOrder is a foreign key field.
Does anyone have any insight into this? What we can do to fix it?
Talk To Other Members
RE: [pervasive][odbc client interface] Numeric value out of range. (#0) - MS Access and Sage 50
Mirtheil
http://www.mirtheil.com
RE: [pervasive][odbc client interface] Numeric value out of range. (#0) - MS Access and Sage 50
We found a work-around by linking JrnlHdr to JrnlRow on PostOrder, then only returning the PostOrder value from JrnlHdr instead of from JrnlRow.
But what is causing those records with the dodgy values? I can't seem to filter them out any other way. And the number of them keeps changing.
Thanks.