PO number field length should go back to 20 characters

Stan, I know this won't be much help but the underlying database has not been changed. It still supports 20 characters in the PO Number. This must have just been a UI change by Microsoft, though I have no idea why such a change would have been made.

Ryan,

Thanks for the reply. I didn't realize the data structure field length was still the same just that the GUI field length didn't go past 15 now. I assumed something chnaged in the data structure upgrade between versions 1.3 and 2.0. That means if MS wants to put it back it should be easier, I would think. I don't know why that would be changed as well.

My customer just wants to be able to type long PO numbers into those fields and cannot do what he used to be able to do.

Thanks

Stan

"Ryan @ RITE" wrote:

I know this may not be as strait forward as it was, but if there is any field that the customer is not using, a SQL trigger could be created to fire when that field is updated and copy that over to the PONumber field in the database.

This was an issue with HQ enviroments, The DB field is 20 char. but HQ adds a chunk of #s to the front of inter-store transfers and PO#s larger than 14 chars. would 'hang" in HQ. The limit was introduced in 1.3r (thankfully for me, this was a big headache)

Ideally the limit should be set when you configure HQ in store ops, but at least for me it's finally there...

There's no way around this without going back to pre-1.3r manager as the .exe is changed (don't have a clue how to undo that).