Anyone on or going to 6.1,
Just a heads up on something that I am dealing with as we prep for the
jump mid next week.
On 6.1 the APInvHed.Company field was changed (can't tell you if it was
an accident or for a reason). All Company fields in the DB are (x)8 by
definition. This one field has been changed to (x)20. This causes any
Crystal reports that used ODBC to link this field to fail. The ODBC
width is 16 for all other Company fields, and 40 for this one. If you
attempt to link the field to another Company field it will warn you of a
potential problem and the link will not work correctly. This does not
affect the standard Crystal reports as they rely on the DBF export files
and not ODBC.
This can be fixed though (If Epicor does not fix it before you get to
6.1). If you use the Epicor Procedure to truncate the ODBC width of the
field to 16 like other company fields the link can then again be
accomplished.
In my case I have had to link via ODBC from the AP Invoice Aging report
back into the database to retrieve additional information. My links
failed until I made the modification.
I thought I would stick this out there before anyone else ended up with
the imprint of their forehead in their desk.
As with most things, I strongly recommend anyone who runs into this
issue call support for a fix and rely on their advice over mine.
Aaron Hoyt
Vantage System Administrator
Hittite Microwave Corporation
[Non-text portions of this message have been removed]
Just a heads up on something that I am dealing with as we prep for the
jump mid next week.
On 6.1 the APInvHed.Company field was changed (can't tell you if it was
an accident or for a reason). All Company fields in the DB are (x)8 by
definition. This one field has been changed to (x)20. This causes any
Crystal reports that used ODBC to link this field to fail. The ODBC
width is 16 for all other Company fields, and 40 for this one. If you
attempt to link the field to another Company field it will warn you of a
potential problem and the link will not work correctly. This does not
affect the standard Crystal reports as they rely on the DBF export files
and not ODBC.
This can be fixed though (If Epicor does not fix it before you get to
6.1). If you use the Epicor Procedure to truncate the ODBC width of the
field to 16 like other company fields the link can then again be
accomplished.
In my case I have had to link via ODBC from the AP Invoice Aging report
back into the database to retrieve additional information. My links
failed until I made the modification.
I thought I would stick this out there before anyone else ended up with
the imprint of their forehead in their desk.
As with most things, I strongly recommend anyone who runs into this
issue call support for a fix and rely on their advice over mine.
Aaron Hoyt
Vantage System Administrator
Hittite Microwave Corporation
[Non-text portions of this message have been removed]