Hi all,

I was wondering if there is an option to enable E-mail redirecting to a single account to prevent Customers in the database from receiving test E-mails?

Thanks.

Attached it a little utility for finding GUIDs in a database - it should work for any SQL Server database, not just an iMIS one.

Enter the GUID (e.g. 6AD322CE-B4CB-4E4B-B8BD-9B86166A18BB) and it will return all the tables and columns in the database where the value occurs, and the number of matches found.

Instead of just reviewing the SQL logs and the logs of your backup program, go ahead and simulate a true disaster recovery scenario. Restore your database backup from last week in full, and from last month in full. To the point where a regular user can login and confirm they are using an old backup of the system.

Steps to take:

TBC

ASI consulting has created ER diagrams for both e-Opps and the entire iMIS for .NET table structure. These are for the 10.6.06 release. We generated these from the schema using a tool called ER Studio. I recommend this tool for anytime one must to understand what relationships are enforced between tables enforced at the database level. It is great help on iMIS conversions.

http://www.embarcadero.com/products/erstudio/index.html

As I was talking with Eric today between sessions, I asked him about naming conventions within business objects, and I came up with a suggestion.

I think it would be a good idea to establish a naming convention for fields in order to separate the standard iMIS fields from those added by the AiSP and user. This would help to protect against upgrade-related fields colliding with customizations.