This problem also appears to be in SO_InvoiceTracking. The field size is 15 characters, however more data is being stored in the field than what the File Layouts state.

This could cause problems. Alnoor is the one person who could tell you what will happen.

I'm not sure what you mean by "this could cause problems"? There's more data in the field than what ODBC pulls. It's been this way for years. The issue is that the ODBC definition doesn't seem to be pulling enough characters in either of those tables.

No, BigLouie is right.  The problem is not the ODBC return, since that uses the table's data dictionary.  The real issue is how the bad data (larger than the data dictionary field size) is getting into the table.  That should be technically impossible.

The field is "StarshipShipVia". The data is being written by Starship.

Yes, but that doesn't mean the data is being written with proper error checking.  If they need more than 15 characters, the field should be made larger (by them / Sage).  The fact they are writing data beyond the character limit is a problem for Starship / Sage to solve.

Since it sounds like this is recurring for you, opening a case with Sage might be a good idea.

It sounds like this is a Starship issue for not writing data within the confines of Sage's data dictionary, or  a Sage issue for not having a field size large enough to accommodate the data coming from Starship. I foresee finger pointing from both parties!

I notice that this is still a problem 6 years later.

I have started cases with both Sage and V-Technologies. I have had multiple emails and calls with both companies. I have even have support reps from both companies on the same call at the same time.

In the end, both companies are pointing fingers at the other. Sage says V-Technologies should increase the size of the field because they are the master developer and V-Technologies says Sage should increase the size of the field because their field size is too small (it's 15 and should be 50).

So it appears there is no resolution and will be no resolution because neither company wants to be the one to help the end users!

I have done testing and it appears you can download the data in full using Visual Integrator export which is slow as molasses. It's not a solution. ODBC should just work. I can't write Crystal Reports out of the AR_InvoiceHistoryTracking file using Visual Integrator.

I can't give V-Technologies any thumbs up for tech support.  I opened a case two years ago between them and Scanco.  No love!