memory error (Access 2000)

[gradyk]

MS Access 2000 runs kind of weird on my XP box, but just fine on the Win98SE boxes --- - sometimes I get the following error and it just locks up: Application error...instruction "0x77f83aed" referenced memory at "0x0000000000". The memory couldn not be "written". I looked into the MS Knowledge base but to no avail. Any ideas? Any way to test the memory in the box...maybe it's the problem.

Thanks in Advance.....Grady

[HansV]

Do you still have the problem, and does it occur in other applications too? If so, you might post a new question in the Hardware forum. The hardware experts probably don't visit this forum very often.

If it's limited to Access, try to find some kind of pattern as to when the error occurs.

[WendellB]

Somehow I missed your post. <img src=/S/blush.gif border=0 alt=blush width=15 height=15> That looks to be a bug in Access 2000, in your install, or possibly indicates the need to upgrade to the current Service Pack. I really don't think it is a hardware error - what the error is telling you is that something in your database or in Access tried to write memory at zero - which is always a no-no. It is also possible that the database is corrupt and needs to be repaired. Hope this helps - let us know how you get on - and again I apologize for missing your post.

[gradyk]

The MS Access 2000 application that I have has SP-3. If it's an error in the database then how would I find where it is trying to write memory at zero? This database is compacted and repaired about 3x per day.
Also, On several occasions I have opened a brand new empy Access Database and imported every single query, table.....module etc from the one that is giving me trouble just to make sure that system files are clean and not corrupted.
Thanks In Advance!
Grady

[WendellB]

Several questions then:<UL><LI>How many users work on the database?
<LI>What sort of VBA modules exist in the database?
<LI>Does the problem always occur on a given PC, but works OK on other PCs?
<LI>Is the database set to automatically compact on close?
<LI>Do you have Autocorrect set to off?
<LI>Do the errors usually occur during a given task or process?[/list]I or others will probably think of more possibilities in the meantime, but this should begin to give us some clues as to what is going on.

[gradyk]

Answers to your questions:
How many users work on the database? Only One, however if I put the database on a WIN98SE box I can have several users on it
What sort of VBA modules exist in the database? No Rocket Science, just simple ones that lookup data when specific criteria is selected.
Does the problem always occur on a given PC, but works OK on other PCs? Yes, Only happens on the XP box. Runs fine on WIN98 SE boxes
Is the database set to automatically compact on close? No, it's done manually throughout the session
Do you have Autocorrect set to off? No it's on, don't really know how to turn it off.
Do the errors usually occur during a given task or process? Seems to happen when printing to Adobe to create a PDF but not all of the time.
Thansk!

[HansV]

>> Do you have Autocorrect set to off? No it's on, don't really know how to turn it off.

Wendell means Name AutoCorrect here.
- Select Tools | Options...
- Activate the General tab.
- Clear the check boxes in the Name AutoCorrect section.
- Click OK
This is a setting for each individual database.

[WendellB]

<hr>Do the errors usually occur during a given task or process? Seems to happen when printing to Adobe to create a PDF but not all of the time.<hr>

That leads me to suspect a problem with the print driver used to create the PDF file. Print drivers are one of the most common causes of application crashes - check and see if there is a later version of the Adobe that is intended for use with Windows XP. Another alternative might be to try one of the other freeware or shareware products that can be used to create PDF documents and see if they cause problems. This of course is conjecture until testing confirms or denies, but sometimes hunches can be a good way of sorting out problems.