Sage 100

Wondering if anyone has a cheat sheet for the debug commands on an error? started a trial conversion on Saturday of a 4.5 to 5.1 upgrade and ran into a file AP_InvoiceHistoryDetail.M4T that errors out on migration and rebuild. I remember there being a combination of question mark and dollar signs that would return the bad record that caused the error. The file has 17K records and looking for a quick way to find the corrupt record.

See if this helps.

Other debug comments depend on the program. You can guess and print variables with ? variableName$ ex: ? InvoiceNo$ ? AccountNo$ ? CustomerNo$ ? ItemCode$ - which would help identify the problem transaction. OR, for way too much info, type in DUMP (return) and get all variables.

Thanks Barbara and Lee, it was just what I was looking for!

Capturing the debug DUMP after an error into a file can sometimes be very useful to search for things of interest. Per Alnoor and a past post here: https://90minds-com.socialcast.com/search?utf8=%E2%9C%93&q=alnoor%20debug%20dump

Capturing the DUMP in a text file allows you to use a text-editor FIND to look for suspect variables.