Error: Object invoked has disconnected from its clients

[Anonymous]

I've written a useful routine that does plotting, in a consistent way across all my drawings without havin to re-setup all the settings each time. Just occasionally i come across a drawing, useful from outside my office, and when i try to plot it I get the above error message, which also generates an unhandled exception and crashes autocad. When i've gone back to the routine and tried to place a few debug points it then proceeds to crash the module as i scroll down it, and has kept doing so each time, until the VBA routine been deleted and replaced by a backup copy, after which its works without a problem at all.

Can anyone give me some idea of whats going on?

[Anonymous]

DVB files are known to become corrupt under certain
circumstances. It's bugs in VBA.

wrote in message news:f152c4d.-1@WebX.maYIadrTaRb...
> I've written a useful routine that does plotting, in a consistent way across all my drawings without havin to re-setup
all the settings each time. Just occasionally i come across a drawing, useful from outside my office, and when i try to
plot it I get the above error message, which also generates an unhandled exception and crashes autocad. When i've gone
back to the routine and tried to place a few debug points it then proceeds to crash the module as i scroll down it, and
has kept doing so each time, until the VBA routine been deleted and replaced by a backup copy, after which its works
without a problem at all.
> Can anyone give me some idea of whats going on?
>

[Anonymous]

Tony, I came across a link that describes an undocumented /decompile switch
for MS Access.http://www.trigeminal.com/usenet/usenet004.asp. It decompiles
the mdb and recompiles it from the pcode. Is it possible to do this in acad?

--
Ed
--

"Tony Tanzillo" wrote in message
news:49D11271FBF8C07449250F98B2A0BD6C@in.WebX.maYIadrTaRb...
> DVB files are known to become corrupt under certain
> circumstances. It's bugs in VBA.
>
> wrote in message news:f152c4d.-1@WebX.maYIadrTaRb...
> > I've written a useful routine that does plotting, in a consistent way
across all my drawings without havin to re-setup
> all the settings each time. Just occasionally i come across a drawing,
useful from outside my office, and when i try to
> plot it I get the above error message, which also generates an unhandled
exception and crashes autocad. When i've gone
> back to the routine and tried to place a few debug points it then proceeds
to crash the module as i scroll down it, and
> has kept doing so each time, until the VBA routine been deleted and
replaced by a backup copy, after which its works
> without a problem at all.
> > Can anyone give me some idea of whats going on?
> >
>
>