We are running AREV 3.12 under Windows 95 with expanded memory active. We are receiving the error message "'RTP57A' Line 215. Variable not assigned a value; zero used." Can anyone help with this issue? It would be greatly appreciated. After entering "#" at the debugger, received the following info:

Statistics after garbage collect:

There are 2,137 descriptors used.

There are 105,772 bytes of string space free.

The PROGRAMS array consumes 143,019 bytes of memory.

This is an environment received from one of our overseas sites and I am able to reproduce the error subsequent to loading it onto my local drive.

Help me…help me…pleeease!!!

Have a great weekend…toodles!

Kimberly

Normally, this type of error comes from either the handle, the key or the record having an unassigned variable.

[email protected]

Sprezzatura Group

Aaron:

hmmm…but how do I fix it?

Thanks,

Kimberly

You'll have to go through the code and see where the unassigned it coming from. If you can narrow it down some, you should be able to find it. If you can't before each read, you'll have to do an IF UNASSIGNED() and check for it. If you don't know where, you could always try an MFS to find it.

[email protected]

Sprezzatura Group

What I normally do in a case like this is to try and determine what variables are being used at that line in the code and then have the routine talk to me by using the following:

(PRINTER OFF) if it has been turned on.

PRINT "THIS IS variablex: ":variablex

PRINT "THIS IS variabley: ":variabley

etc

PRINT "OK? ":; INPUT Q,2 ; IF Q=N' THEN STOP

The input statement forces the routine to stop and allow me to read the variables that are being used. Usually, the variable is null or is text.

This way I can track down strange stuff or if the varible(s) are being initialized.

Dale

I do that as well when the system's local, but when I can't find it, or, like in this case, the system is thousands of miles away, the MFS can be easier.

[email protected]

Sprezzatura Group

View this thread on the forum...