I have a problem with the GL Journal Listing report data from a
particular day. If I include that day in the report listing, I get this
error:
"Failed to enable constraints. One or more rows contain values
violating non-null, unique, or foreign key constraints."
I get this from Crystal Reports as well if I try to refresh the
Journal.rpt report with this data.
This is a general ADO.NET/System.Data exception, so the problem is
something in the DataSet that violates the constraints in the xs:schema
definition embedded in the file.
I just can't see what it is. As far as I can tell, all of the data
constrained by the xs:unique sections are valid - no null values, no
duplicate values. Its less obvious to identify a FK relationship...I'm
not sure I understand the schema definition completely. I thought I had
it identified to the RowID value, but its just not easy to visually find
the differences.
Is there a tool that can process this file and tell me what the
violation is? I have a case open with Epicor, but haven't heard back
(and the tech on Friday wanted me to send them my database with some
hand-wavy comments about 'database issues'. I just did a 'divide in
half' search several times in the date range of the problem data to find
the day, so I shouldn't have to send them 3GB of data to find what is a
simple problem with the report's assumptions about the data that Vantage
emits.
-bws
--
Brian W. Spolarich ~ Manager, Information Services ~ Advanced Photonix /
Picometrix
bspolarich@...
<mailto:bspolarich@...> ~ 734-864-5618 ~
www.advancedphotonix.com <http://www.advancedphotonix.com>
[Non-text portions of this message have been removed]
particular day. If I include that day in the report listing, I get this
error:
"Failed to enable constraints. One or more rows contain values
violating non-null, unique, or foreign key constraints."
I get this from Crystal Reports as well if I try to refresh the
Journal.rpt report with this data.
This is a general ADO.NET/System.Data exception, so the problem is
something in the DataSet that violates the constraints in the xs:schema
definition embedded in the file.
I just can't see what it is. As far as I can tell, all of the data
constrained by the xs:unique sections are valid - no null values, no
duplicate values. Its less obvious to identify a FK relationship...I'm
not sure I understand the schema definition completely. I thought I had
it identified to the RowID value, but its just not easy to visually find
the differences.
Is there a tool that can process this file and tell me what the
violation is? I have a case open with Epicor, but haven't heard back
(and the tech on Friday wanted me to send them my database with some
hand-wavy comments about 'database issues'. I just did a 'divide in
half' search several times in the date range of the problem data to find
the day, so I shouldn't have to send them 3GB of data to find what is a
simple problem with the report's assumptions about the data that Vantage
emits.
-bws
--
Brian W. Spolarich ~ Manager, Information Services ~ Advanced Photonix /
Picometrix
bspolarich@...
<mailto:bspolarich@...> ~ 734-864-5618 ~
www.advancedphotonix.com <http://www.advancedphotonix.com>
[Non-text portions of this message have been removed]