Custom Store Procedure/Tables Cannot reside within Manex Database

Upon recent review of your Manex data files we have come across some concerns that we need to make you aware of. 

We have found that you have many custom procedures, views and/or tables within our (Manex) database.  

Some of these Procedures start with "  ". . . . or "    " . . . but other's do not have any type of label or indicator for us to tell if this is a custom file or not.  

The issue with placing these Custom Procedures, Views, Etc. . . directly within the Manex Database is that any of our updates and/or conversions will go through and find any procedure, View, Table, etc . . that we (Manex) did not create and/or need and automatically remove them from the database.  This means that you will potentially lose all of these custom items you have created directly within the Manex Database.  

You need to make sure that all custom procedures, views, tables, etc . . are created and saved within a database outside of MANEX.  You can create the procedures to link to and use the Manex database, but they can not reside within the Manex database itself.  We suggest that you work with IT on moving these out of Manex database and let us know if you have any questions.