Debugging Run Time Error In Distributed App

funderburgh

Registered User.
Local time
Yesterday, 22:14
Joined
Jun 25, 2008
Messages
118
I maintain a distributed application and I occasionally get run time errors when I introduce a new version or process. Almost always it is because the app cannot access some resource it needs, like I failed to link a new table. The error does not produce an error number or log I can use to debug the problem, but I always know what I changed and have been able to sort out the issue. This time around I introduced a report produced in Excel and I am getting a run time error in the distributed version, and I can't see any holes the the upgrade. Any thoughts on how to go about debugging the error?
 
Does your code use Error Trapping?

A report produced in Excel: Are you setting an object reference to Excel? Or are you using a built-in save as Excel function?
 

Users who are viewing this thread

Back
Top Bottom