All of a sudden, any attempt to open any form that inherits from my base MID
Child form gives this error:

An error occurred while loading the document. Fix the error, and then try
loading the document again.


File or assembly name ErrorObject, or one of its dependencies, was not
found.

KB 814732 comes close to being the same, but not exactly. This application
worked fine until my colleague had her computer id changed to correct a 'Z'
to a '2' while some items were checked out from VSS.

My biggest fear is having to recreate 20+ MDI forms from scratch. There has
to be a better way, right?

"Fred Morrison" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> All of a sudden, any attempt to open any form that inherits from my base
MID
> Child form gives this error:
>
> An error occurred while loading the document. Fix the error, and then try
> loading the document again.
>
>
> File or assembly name ErrorObject, or one of its dependencies, was not
> found.
>
> KB 814732 comes close to being the same, but not exactly. This
application
> worked fine until my colleague had her computer id changed to correct a
'Z'
> to a '2' while some items were checked out from VSS.
>
> My biggest fear is having to recreate 20+ MDI forms from scratch. There
has
> to be a better way, right?
>

A common reason for seeing this in my own code was things happening in the
Load event of the base MDI child. It gets fired by the IDE in this
scenario.

I can't explain how your colleague's machine name change might have affected
this, though. Only that some code is running at design-time which is
somehow sensitive to the change. Protecting it with a test for
Me.DesignMode would defer the error until runtime, but at least you won't
have to re-work forms.

Best Regards,

Andy