modal dialogs

[Mark Terry]

On Mar 12, 2008, at 3:32 PM, James Rea wrote:

> The odd part is the dialog. I know you (Jim Cook) have had this  
> problem
> before, but it hasn't appeared on any other server that I know of.  
> What
> it should do is throw up an error message on the browser, just like  
> any
> other code error. The standard error display gives you information on
> what procedure contains the problem, and where. Without that  
> information
> it's going to be pretty difficult (though not impossible) to track  
> down
> the implicit assignment.
>
> The next server version will have an option to completely disable all
> alerts. This shouldn't be necessary, and hasn't been anywhere else,  
> but
> it should prevent any alerts from appearing on your server. With this
> option turned on you can't do any kind of manual work on the server at
> all, because normal alerts and dialogs don't work either. Of course
> doing manual work on a server is not usually a good idea anyway. There
> will be more info on this in the release notes for the new version  
> when
> it is available.

Implicit assignment problems have always meant corrupted data for me,  
so I would think a dialog would be critical. Since the assignments are  
disabled on the server, no damage can occur, it seems, but if the  
underlying/original file still has the "loose statement" in a proc, it  
sounds like a problem just waiting to happen. Too bad there's not some  
way to log the active field or var when encountered.