Re: Runtime error 381 in VB app

From: Bob O`Bob (filterbob_at_yahoogroups.com)
Date: 02/19/04 

Date: Thu, 19 Feb 2004 12:23:53 -0800

=?Utf-8?B?TWlrZQ==?= wrote:

> I am not sure if it is VSPrinter that is causing this error. This is the scenario.
> The app runs fine in my desktop but fails in another users..that is why I am not
> able to debug and get to the point that this is failing.
>
> And also it will be helpful for me if I know what this error is and why is this caused?
>
> I am on a hit and trial method here. Since this behaves differently in two machines.
>
> Any idea is appreciated.

Ken's hit it right on the money.
You probably need to ship that customer an "instrumented" version of the program,
compiled with [excessive amounts of] error trapping in the relevant procedures.
That way the next time it happens they can tell you more about exactly what's
going wrong and where. In fact you should probably consider adding a log file to
track all user/file/whatever interactions, record all errors there too, and when it
happens again just have them ship you that file.

        Bob
BTW, I used to do second-line tech support for the makers of VSPrinter... 

-- 
looking for work again  <http://obob.com/bob/resume/>

Relevant Pages
Loading