Sage 200 Professional - Allowing Sage 200 to ignore custom tables in the database

Table extensions can contribute to 'Out of Memory' and ‘Time Out’ errors. The reason is that they can act as a multiplier when the system is interrogating SQL data.

NOTE: This article has been prepared and issued to you as a goodwill gesture only and Sage accepts no liability or responsibility for its use. For further support please refer to your Business Partner.

Renaming the SageObjectStoreMerged.Addin file which resides in the ObjectStoreExtension folder (%USERPROFILE%\AppData\Local\Sage\Sage200\ObjectStoreExtension) will cause a client machine to ignore any table extensions in SQL.

We would only endorse this file being renamed temporarily on a client machine to get around these kind of problems but only after due diligence has been followed (by testing off site etc).

It would also be imperative that the file is renamed back immediately as failure to do so will most likely cause customisation's to Sage 200 not to function correctly.