Q to dev.: Why OpenSQL errors are not handled with On Error?

[ZvezdanD]

Please developers, this is really annoying.

[trixmoto]

You can easily do this yourself in the script. In fact it's better if you do it yourself because you built the SQL so you know what it's doing and can therefore display a more helpful error message.

[ZvezdanD]

You can easily do this yourself in the script. In fact it's better if you do it yourself because you built the SQL so you know what it's doing and can therefore display a more helpful error message.

I think that you didn't understand me. This is exactly what I want - to handle all VBScript errors by myself. For example:

Code: Select all

On Error Resume Next
Set oIter = SDB.Database.OpenSQL("SELEC")

This will display unneeded error message, even if there is On Error in the front of the wrong line. Other VBScript errors are handled with On Error Resume Next without a problem. Maybe I should use a term "catched" instead of "handled". Sorry for my bad English.

[trixmoto]

Oh, I thought I'd done this before without any problems. Maybe that was in MM2 and I've not re-tested in MM3 yet.

[ZvezdanD]

Oh, I thought I'd done this before without any problems. Maybe that was in MM2 and I've not re-tested in MM3 yet.

Actually, it is same behavior in MM2, as in MM3. I just tried it.

[Lowlander]

This should be fixed, can you confirm: http://www.ventismedia.com/mantis/view.php?id=6709