Sean, if you have FM3 in the program this assertion will fire.
Easiest solution is you can comment it out and the assertion at line 527.
In Clarion10 there is a new global template setting you can set in the data dll, but it requires you to set it for every table in your dictionary. Not very useful.
Since you’re not actually calling CLOSE(Company)
then I wouldn’t just suppress the message, It’s there to help you.
If you do have a valid reason to suppress the message, you can use my debuger class
which hooks assert, and has a special match system to look for messages and decide what to do with them.
I wrote that match system for Kelly Major, who was closing a file outside of ABC and the abc method was messing with him.
see the notes in the Debuger.AddAssertMsg method for this exact assert message
This may be a long shot but I have been caught out by using the same name for two elements that are not the same structure. CLOSE() is quite an overloaded function. Normally the compiler gets confused, so you can’t complete but it might get through and the wrong thing gets closed in compiling. It might be worth searching the whole project for ‘COMPANY’ just in case you have another COMPANY structure that gets closed too?