![]() The idea is that once an error occurs and execution goes inside the error handler it is temporary deactivated and *parent* error handler becomes active. I get an error 76 in DownloadTemplates but when coming back in Form_Load sub, Form_Load_Error: is not triggered, it goes on on following line !Įnd FunctionNote that Test0 function will error out on 12345 / 0 inside the error handler while Test1 and Test2 will successfully silence the error. ![]() To verify this I've simulated a 76 error in DownloadTemplates sub (I've modified "\Templates" so that path doesn't exist) : ![]() 15360 If Myver G_TempVer Then DownloadTemplates <= Error 76ġ7180 On Error GoTo DownloadTemplates_Errorġ7460 If Err.Number = 58 Or Err.Number = 76 Thenġ7470 MsgBox "Impossible de créer le répertoire " & G_AppData & "\Templates\" & Rootitem.Name, vbExclamation, Captionġ7480 fPath.DeleteFolder (G_AppData & "\Templates"), Trueġ7510 ErrHdl ("DownloadTemplates dans Angles - Folder " & G_AppData & "\Templates\" & Rootitem.Name)Įnd SubError 76 triggers DownloadTemplates_Error:īut as the error is not cleared, when exiting the DownloadTemplates sub, coming back in Form_Load sub, Form_Load_Error: is triggered on line 15360.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |