The problem is a performance issue that could cause lengthy delays when anyone is using the MagicAuto functionality. (i.e. Map Magic plugin for ArcGIS) The delays may be experienced by any user of Crash Magic Online while another user is creating a new diagram using MagicAuto.
The problem we've identified involves the way in which MS SQL Server handles table locking when using transactions. Crash Magic Online opens a "transaction" when preparing to create an automated report using MagicAuto. That transaction "wraps" the use of several tables in the system. Once this transaction is begun those tables appear to become unavailable for other users until the transaction is "committed". Since some of those tables are integral to the use of the program, it may become impossible to navigate Crash Magic until the MagicAuto diagram request is completed.
At this time, it does not appear that installations using Oracle's SQL server will experience this problem.