Sage 100

Welcome to the Sage 100 Support Group on Community Hub! Available 24/7, the Forums are a great place to ask and answer product questions, as well as share tips and tricks with Sage peers, partners, and pros.

Error 88 on Sales Order Entry Lines

Posted By SilverFox 10 months ago

We are experiencing an error 88 on Sales Order Lines. The error occurs only on large orders with numerous lines, especially when adding inventory items to the order on the fly. The line prewrite script is failing and referencing different UDT objects declared by the Set command. The failure normally occurs on MoveFirst of MoveNext commands for the UDT objects. The prewrite script is lengthy and sets numerous new objects for other table reading, prior to writing the SO line record. If an error occurs, all data on the lengthy order is lost. How can we better manage the object resources to avoid the crashes?

0 Kevin M 10 months ago

When done with a new object created via script, I set it to nothing (before the end of the script, including before any early exits).

set oUDT123 = nothing
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 SilverFox 10 months ago in reply to Kevin M

Kevin,

This is for a script executed on the Sales Order Detail Pre-write event. Is setting to nothing effective for scripts tied to sage events?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Kevin M 10 months ago in reply to SilverFox

Yes, but not always. Don't do that for objects created from a ChildHandle, or from a property (like creating oLines from a header object).

You'll see examples doing this:

if not(IsObject(oUDT123)) then ...

...when creating objects, to avoid trying to create an object that already exists, but I think it's cleaner to close things out purposefully.

Do whatever works.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Sage 100

Error 88 on Sales Order Entry Lines

COMMUNITY

COMPANY

PARTNERS

SUPPORT & TRAINING