Trap for missing DLL 1

[hdougl1]

I have a VB app that instantiates a dll located on a network server. How can I trap the error generated when access to the dll is lost, such as the network is down etc. While trying to test for this error in the IDE with the dll properlly registerd but not located in the specified location I get a error on the declaration. Theres no specified vb error number.
Thanks in advance

 

[FRoeCassNet]

Not sure what you mean by the IDE gives you an error on the declaration. It shouldn't really care about the declaration itself, just the scope of it (public, private, etc.) When you go to call the function in the DLL you should get an error #54 (file not found) though.