The executable is created on my new PC and placed on a corporate server. Upon execution of the app on the server it encounters a '429' error. The application has not been updated in several years. When updating the code, the test version of the DLL I believe to be the culprit, was missing from the reference list. I located the DLL, re-registered it (new comp recently) and the application ran and tested fine.
Q1: Is there a way to determine which DLL/OCX could be causing the '429' error?
Q2: The existing executable uses the registered server version of DLL, how does the new executable find and use the DLL on the server?
FYI. This single app is not the only app that uses the DLL in question.
I have not coded in VB6 in 7-8 years and am completely out of practice. All responses greatly appreciated. Thanks.
Q1: Is there a way to determine which DLL/OCX could be causing the '429' error?
Q2: The existing executable uses the registered server version of DLL, how does the new executable find and use the DLL on the server?
FYI. This single app is not the only app that uses the DLL in question.
I have not coded in VB6 in 7-8 years and am completely out of practice. All responses greatly appreciated. Thanks.