[AccessD] Intentional Errors

We use the ON ERROR RESUME NEXT clausule to try and check intentional
Errors. Where you put the intentional error use the next code:

if err.number<>0 then
	'clausule for take the error control
	'remember be sure to put 0 on err.number for the next intentional error
	err.number=0
endif


Juan Menendez
Mastercafe

-----Mensaje original-----
De: accessd-admin at databaseadvisors.com
[mailto:accessd-admin at databaseadvisors.com]En nombre de Heenan, Lambert
Enviado el: miércoles, 12 de marzo de 2003 23:40
Para: Access-D Email (E-mail)
Asunto: [AccessD] Intentional Errors


Would anyone care to try to explain what could possibly be a problem with
executing code which executes a statement that will either succeed or will
generate an error, such as the recent "Am I a subform?" thread.

As long as the error is being trapped, what would make anyone "uneasy" about
this technique. To me it seem a perfectly valid approach, and to anyone who
has ever written C++ or Java code it's second nature. That's what exception
handling is all about.

Try {
	//Some Code that might Error
}
Catch {
	//Handle the error condition
}


Lambert
_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com