Re: Access database that works in 2000 crashes in 2003 when editing co



Are you able to open the VBA window in another database, such as
northwind.mdb that installs with Access?

No: there is a problem with the Access/VBA install. If you have any VBA
add-ins, see if you can remove them. If you have recently installed other
software (even VB.NET), remove it. If nothing else works, remove and
reinstall Office 2003.

Yes: there is a problem with the code in this particular database. Try this
sequence:

1. Uncheck the boxes under:
Tools | Options | General | Name AutoCorrect
Explanation of why:
http://allenbrowne.com/bug-03.html

2. Compact the database to get rid of this junk:
Tools | Database Utilities | Compact

3. Close Access. Make a backup copy of the file. Decompile the database by
entering something like this at the command prompt while Access is not
running. It is all one line, and include the quotes:
"c:\Program Files\Microsoft office\office\msaccess.exe" /decompile
"c:\MyPath\MyDatabase.mdb"

4. Open Access, and compact again.

5. Open a code window.
Choose References from the Tools menu.
Uncheck any references you do not need.
For a list of the ones you typically need in your version of Access, see:
http://allenbrowne.com/ser-38.html

6. Still in the code window, choose Compile from the Debug menu.
Fix any errors, and repeat until it compiles okay.

At this point, you should have a database where the name-autocorrect errors
are gone, the indexes are repaired, inconsistencies between the text- and
compiled-versions of the code are fixed, reference ambiguities are resolved,
and the code syntax is compilable.

If it is still a problem, the next step would be to get Access to rebuild
the database for you. Follow the steps for the first symptom in this
article:
Recovering from Corruption
at:
http://allenbrowne.com/ser-47.html

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Bill Bradbeer" <billbradbeer@xxxxxxxxxxx> wrote in message
news:0F68AA82-99BD-4DEC-B147-938409D10256@xxxxxxxxxxxxxxxx
I have a database that functions without problems in 2000 or 2002 that I
need
to open and modify in 2003. When I open the VB Code window I get a fatal
error and if i just open a single form's code and try to change anything,
it
similarly crashes.

Is this a known problem with Access 2003, and if so, is there a upgrade
that
can be installed?
--
Bill Bradbeer
SteepleTower Software Ltd
United Kingdom


.



Relevant Pages

  • Re: Message Alert
    ... You or another user can press the F11 key to show the database window ... So the two strSQL lines needs to be changed also: ... assembled strSQL by pressing Ctrl + G, which opens the Immediate ...
    (microsoft.public.access.modulesdaovba)
  • Re: filter sort error - crash!
    ... Compact the database to get rid of this junk: ... Open a code window. ... Uncheck any references you do not need. ... Still in the code window, choose Compile from the Debug menu. ...
    (microsoft.public.access.forms)
  • Re: Event Procedure to Preview Report closes Access
    ... Compact the database to get rid of this junk: ... Uncheck any references you do not need. ... Still in the code window, choose Compile from the Debug menu. ...
    (microsoft.public.access.reports)
  • Re: Will a compiled kernel run faster/better?
    ... > kernel you get with your distro, and one that you compile yourself? ... How long does it take a KDE window to come up? ... the database stuff running at normal priority. ...
    (comp.os.linux.misc)
  • Re: Access/Comcast/Digital Conversion
    ... I did use the Shift-Key trick and that did open the database object window. ... Tony Toews, Microsoft Access MVP ...
    (microsoft.public.access.tablesdbdesign)