I have a multi-tier application.
Application A (VB.NET) creates security object B (VB6) which then creates a data access object C which raises an error.
When the data access object is a VB6 object then the error is correctly handled by the security object (B) but when I replace it with a VB.NET object raising the same error, the error appears to be returned straight to the main application (A) which is not expecting it.
Has anyone seen this behaviour or got any suggestions for a work-around?
Glyn.
Application A (VB.NET) creates security object B (VB6) which then creates a data access object C which raises an error.
When the data access object is a VB6 object then the error is correctly handled by the security object (B) but when I replace it with a VB.NET object raising the same error, the error appears to be returned straight to the main application (A) which is not expecting it.
Has anyone seen this behaviour or got any suggestions for a work-around?
Glyn.