Re: running report cause fatal error- on Win98, not XP
- From: "Allen Browne" <AllenBrowne@xxxxxxxxxxxxxx>
- Date: Sat, 25 Feb 2006 10:12:34 +0800
Riley, it is hard to know where to start, because there are so many possible
factors.
First step might be to check that the Win98 mahine has SP3 for Office 2000
installed (see Help | About in Access).
Also that it has SP8 for JET 4 by locating the file msjet40.dll (typically
in windows\system32), right-clicking and under Properties choose the Version
tab. You should see 4.0.8xxx.0. The xxx digits don't matter, but if you do
not see the 8, download SP8 for JET 4 from:
http://support.microsoft.com/gp/sp
http://support.microsoft.com/kb/239114
Now that you have the same query engine running on both machines, you may be
fine. If not, there could be a corruption in the mdb, and it might be due to
the fact that A2003 and A2000 use different binaries. In a perfect world,
Access would handle the conversion back to A2000 seamlessly; in reality, if
often needs a decompile to get this to work correctly.
Try this sequence:
1. Using A2003, uncheck the boxes under:
Tools | Options | General | Name AutoCorrect
Explanation of why:
http://allenbrowne.com/bug-03.html
2. If you have any code that runs on startup (e.g. a startup form, or
AutoExec macro), disable it. Then compact the database:
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, without opening any code window, or
running any code.
5. Using A2000, create a new (blank) database.
Immediately uncheck the Name AutoCorrect boxes.
6. Import everything from the old database:
File | Get External | Import
7. 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
8. 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.
More info on 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.
"Riley" <CDStendel@xxxxxxxxxxx> wrote in message
news:ep5YgYYOGHA.1132@xxxxxxxxxxxxxxxxxxxxxxx
I'm baffled on this one. I have written a Preventative maintenance
database for our shop. I wrote it using Access2003 on my laptop. The
computer that will be running it is older and running win98 and Office
2000. I wrote the database in Access 2000 format. The database runs 100%
fine on my laptop and the other computers that run XP in our office, BUT
on the computer that will be running it (the older machine) I get a
complete access crash when I try to run a couple of the reports. These are
a couple of reports that are generated by a pretty complex series of
queries. Most of the reports are fine, and print fine, but these more
complex reports generate an error popup and Access shuts down.
I have NO idea where to start on this one, any help would be appreciated.
Like I said, the XP machines run it 100% fine.
Thanks in advance.
Riley
.
- Follow-Ups:
- References:
- Prev by Date: Help on subreport
- Next by Date: Re: Memo Field in a Report
- Previous by thread: running report cause fatal error- on Win98, not XP
- Next by thread: Re: running report cause fatal error- on Win98, not XP
- Index(es):
Relevant Pages
|
