Manufacturing, Distribution, and Internet Applications

[TRoop]

Hi folks...

It seems our ability to print Transfer Orders has stopped working entirely. If you are in "Enter Transfer Orders", load a transfer order and click the "Print" icon on the toolbar, you get the following message box error...

MODULE:   COMPANY:   XXX   APPNAME: General Report

Error 6  occurred at frmPrintReqs  in Procedure IInitializeReport

Overflow

This application will now close

I then tried printing a transfer from the "Print Transfer Orders" menu item. This generates no error but just beeps and then no application screen is displayed.

I have a ticket open on this already but I am wondering if anyone has run across this before??

I am at a loss on this one...

[JohnHanrahan]

Could be that you have a integer value that's greater than 32754 (or there abouts).  Sometimes variables are defined as Integer in VB which only goes up to 32754 (or so) signed.  SQL allows 2 billion and some.  I'm guessing though.

John

[TRoop]

I would typically agree... but this happens on ANY order. I would think that the scenario you are describing would hold true for a specific order...  (please tell me if I am misunderstanding...)

We literally can't print any transfer orders at all right now.

[rsisk101]

Does this happen on every computer? Any new printers added lately?

[TRoop]

We are running in a Citrix environment with approximately 26 client servers dedicated to Mas 500. It is happening on all of them.

[TRoop]

as far as new printers...  none. and no updates over the weekend to any of the servers (this was working fine Friday).

[TRoop]

Just for kicks, I decided to take a look at our "max" TrnsfrOrderkey value since this seemed to be a likely culprit. Right now that value is 36131. I am seriously hoping that this integer value in particular, isn't the case   

I am actually thinking this value is too high to be the culprit all of a sudden...

[JennyWilson]

Sounds to me like the variable for the key is defined as an integer instead of a long.   If this is the case, you'll need a code fix -- I see you've already reported this to CS.

Jenny

[emillspaugh]

I agree that it is a bad variable declaration.  Probably not related to the transfer order key though.  I would assume that is from the key that is used for the session id for the report.  Can you tell me what the value of NextKey is from the following query:

SELECT * FROM tciSurrogateKey
WHERE TableName = 'timPrintTrnsfrWrk'

If that is over 32767, then there is most likely a variable handling that value defined as an INT that should be a long.  And that will need a code change to correct.

Eric

[TRoop]

timPrintTrnsfrWrk = 6427