Sure, but please keep in mind that that's not InfoPath-related and the best
place to ask such questions is in one of the .NET newsgroups. We try to limit
the questions posted here to InfoPath.
Put your code between a try-catch block as follows:
Try
' Code goes here
Catch ex As Exception
Dim message As String = ex.Message
End Try
If you debug your code, you will see the error message in the "message"
variable. Alternatively, remove all error handlers that you currently have
and InfoPath should show you a message box with an error if an error takes
place.
---
S.Y.M. Wong-A-Ton
> No idea since the err.number, err.description I'm use to in VBA doesn't seem
> to work. All I know is that the code goes via the ErrorHandler: displays a
[quoted text clipped - 21 lines]
> > >
> > > H
Humphrey - 05 Jan 2008 02:05 GMT
Thanks I'll test that out. But do you see any problem with my original
InfoPath code?
> Sure, but please keep in mind that that's not InfoPath-related and the best
> place to ask such questions is in one of the .NET newsgroups. We try to limit
[quoted text clipped - 40 lines]
> > > >
> > > > H
S.Y.M. Wong-A-Ton - 05 Jan 2008 03:14 GMT
No, it looked fine to me. That's why I asked what kind of errors.
---
S.Y.M. Wong-A-Ton
> Thanks I'll test that out. But do you see any problem with my original
> InfoPath code?
[quoted text clipped - 43 lines]
> > > > >
> > > > > H