Access 2000 Database becomes corrupted when changed on XP Machine

[Pargat]

I have an Access 2000 secured database sized over 1.0GB. Each and every
time I make even a tiny change to it on XP machine, it becomes corrupted.
Compact and Repair doesn't work.
I have to take it to an old NT 4 box, back out and changes, re-do the
changes, then compact and repair. Has anyone seen this? If so, can you
please suggest a solution. Here's a bit more details:
CPU: Intel Pentium 4
OS: Windows XP Professional version 2002 - SP 2
Office Version: Microsoft Office 2000 Premium
Access Version: Access 2000 (9.0.6926 SP-3)

 

[Gina Whipp]

Pargat,

How does it become corrupt? What is the message? Might be a refrence
problem, that would be my first check. Are you bringing the *.mdw the
database over to the XP machine?

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" - Tremors
II

http://www.regina-whipp.com/index_files/TipList.htm

 

[Pargat]

Thanks Gina for your reply.

The usual error is: "Error accessing network file." It comes up on all
forms. Both MDB and MDW files are used on XP machine. I only use NT box
for compacting and repairing.

 

[Gina Whipp]

Pargat,

Are these linked tables? OR are you tyring to access the database on a
network drive? Either way, sounds like you are trying to do the Compace &
Repair across a network and the connection sneezes. Not an Access message,
more like a Network message/issue.

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" - Tremors
II

http://www.regina-whipp.com/index_files/TipList.htm

 

[Larry Kahm]

I experienced this on a machine that had recently been equipped to support
Access 2000 development.

It seems that Office 2000 SP3 was required. See the following article:
http://articles.techrepublic.com.com/5100-10878_11-5230612.html

Hope that helps!

Larry

 

[Dirk Goldgar]

Thanks Gina for your reply.

The usual error is: "Error accessing network file." It comes up on all
forms. Both MDB and MDW files are used on XP machine. I only use NT
box
for compacting and repairing.

It sounds to me as though you may have been bitten by the nasty bug
described in this KB article:

http://support.microsoft.com/default.aspx?scid=kb;[LN];304548

Office 2000 SP3 fixes the bug, but that won't repair your corrupted
database. You'll have to resort to a backup, or else try importing all
objects to a new database -- some objects probably won't import, and you'll
have to recreate them from scratch. When you do import the objects, unless
you've applied the service pack, it is *crucial* that you compile and save
the project before closing the database.