Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsFormsForms ProgrammingQueriesModules / DAO / VBAReports / PrintingMacrosDatabase DesignSecurityConversionImporting / LinkingSQL Server / ADPMultiuser / NetworkingReplicationSetup / ConfigurationDeveloper ToolkitsActiveX ControlsNew UsersGeneral 1General 2
Access DirectoryToolsTutorialsUser Groups
Related Topics
SQL ServerOther DB ProductsMS OfficeMore Topics ...

MS Access Forum / Forms Programming / May 2005

Tip: Looking for answers? Try searching our database.

Runtime Error! when form is opened in design mode

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Jim D. - 06 May 2005 02:50 GMT
I have an Access 2000 file version application that I like to design on my
Access 2003 SP1 machine.  Lately, when I open a particular (most of them
actually) form in design mode and then hit Alt-F11 to open the VBA editor,
this error message displays (the dialog box is entitled: Microsoft Visual C++
Runtime Library):
=====================
Runtime Error!

Program: C:\Program Files\Microsoft Office\OFFICE11\MSACCESS.EXE

This application has requested the Runtime to terminate it in an unusual
way.  
Please contact the application's support team for more information.

OK (command button)
====================

The error also happens if the VBA editor is already open and I try to design
the form.

Over the last few months, this problem has come and gone.  There have been
periods of time where I can do a few weeks of development without the problem
happening.  Now, it has been several days and no change.

The machine profile is Win XP Pro SP2, Office 2003 SP 1, SQL Server 2000 SP3a.

Any ideas would be much appreciated.
David Cleave - 06 May 2005 11:39 GMT
Hi Jim

I don't know if this is strictly relevant to your problem but I often find
if I move a database between machines running 2000 and 2003 that forms or
reports can become corrupted and crash the database whenever you try to open
them at all.

Copying the corrupted form or report from an earlier version of the database
fixes this problem.

Cheers

David

> I have an Access 2000 file version application that I like to design on my
> Access 2003 SP1 machine.  Lately, when I open a particular (most of them
[quoted text clipped - 23 lines]
>
> Any ideas would be much appreciated.
Jim D. - 06 May 2005 18:16 GMT
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
even after I have been crashing it on the other machine.

Any other ideas out there?

> Hi Jim
>
[quoted text clipped - 37 lines]
> >
> > Any ideas would be much appreciated.
omarty@absys-beziers.com - 23 May 2005 15:51 GMT
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.
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.