Jim D. a écrit :
> Thank you for the reply, but this is not (I don't think) the problem because
> the file works fine on my Win 98 SE / Access 2000 SR1 development machine
[quoted text clipped - 41 lines]
> > >
> > > Any ideas would be much appreciated.
I have the same problems on my config (Win XP Pro SP2 , Office 2003 SP
1)...
I tried to reproduce the Alt-F11 (or form design while VBA Editor is
open) crash on an empty database.
No crash at all...
If I try the Alt-F11 shortcut on another form within the same app, no
problem...
It seems that it's related to a specific malformed form... But How can
i find out where the problem is ?
Any ideas would be much much appreciated !!!
Jim D. - 25 May 2005 20:45 GMT
I think I may have solved it. I removed and reinstalled my printer and
haven't had a problem since. What made me think of this is that when I tried
to print an Access report to my eFax one time, it seemed to break my printer
installation. Access isn't very helpful when it runs into errors related to
printers, it usually just doesn't display the report with no indications.
Hope this helps.
> Jim D. a écrit :
> > Thank you for the reply, but this is not (I don't think) the problem
[quoted text clipped - 73 lines]
>
> Any ideas would be much much appreciated !!!
omarty@absys-beziers.com - 31 May 2005 18:06 GMT
I tried this on my computer, and at first I just remove the "Microsoft
Document Imaging Printer" stuff...
I didn't remove nor reinstall my other printers...
Miracle ! It works... but why ?
Thank you.
PS : Some days ago, I opened a new support ticket at microsoft on this
subject. They are investigating...
I'll keep them in touch with this workaround. It could be usefull for
other people.