Records visible in Access 2K not visible in XP

[Steve Claflin]

I have a database with a moderate number of records in several tables
(the biggest table at the moment is about 800 records). In development
it got moved between 2K and XP repeatedly. Several days ago, it
wouldn't open, and proposed creating a backup before fixing. OK, but
the "fixed version" didn't open -- same messages as the original -- but
the backup did. But, in the 800 record table only 200 records
appeared. We went back several days of daily backups, and opened one of
those (which presumably had worked for several days after the backup).
It opened fine, but stopped at the same record.

So I emailed a copy of that file to work on in a different location,
where Access 2K is in use, and, lo and behold, all the records were
there. I did a compact and repair, sent it back to XP, and still only
see 200 records. We've since verified that even in the most recent
version, the one that wouldn't open in XP) 2K can see all the records.

Has anyone else come across this? And, if so, is there a known strategy
I can use to rebuild the tables in XP (like delete all records, send
from 2K to text, import text into XP, etc.)?
--
Steve
--
http://www.steveclaflin.com

[Steve Claflin]

Steve Claflin wrote:

Allen,

Thanks for the info. I'll have to check the files that you mentioned,
but can't see anything on my Access 2000 Help About that indicates SP
level (although I'm pretty sure I remember downloading that one). I do
ge a build number -- in the first about screen it says 9.0.2720, while
in System Information it says build 2719.

The database in question seems to work fine in Access 2002 as well as
2000, but still has problems in XP. Are there separate service packs
for XP as well?

Allen Browne wrote:

1. Check your service packs.
Your Access 2000 installation should be up to SP3.
Your Access 2002 installation should be up to SP2.
Help | About should give you this info, and the packs can be downloaded from
support.microso ft.com.
You may also like to check the versions of these 2 files match on your 2
computers:
- msjet40.dll (in windows\system3 2), and
- dao40.dll (in \program files\common files\microsoft shared\dao).

2. Steps to Repair.
a) Delete any relations this table is involved in. Delete any indexes in the
table. Verify there are no hidden indexes left, by opening the Immediate
Window (Ctrl+G) and entering:
? CurrentDb().Tab leDefs("tClient ").Indexes.Coun t

b) Create a new (blank) database. Use either version, but presumably you
want the 2000 file format if creating with 2002.

c) Before doing anything else, turn off the "Name AutoCorrect" options
under:
Tools | Options | General.

d) Import the problem table: File | Get External | Import. Check that all
800 odd records are present. Import all the other objects. Recreate the
indexes and relations for this table.

Provided both versions are up to date, you should be able to move back and
forth between the versions.

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html

"Steve Claflin" <Pi********@cs. compost> wrote in message
news:3F******** *******@cs.comp ost...

I have a database with a moderate number of records in several tables
(the biggest table at the moment is about 800 records). In development
it got moved between 2K and XP repeatedly. Several days ago, it
wouldn't open, and proposed creating a backup before fixing. OK, but
the "fixed version" didn't open -- same messages as the original -- but
the backup did. But, in the 800 record table only 200 records
appeared. We went back several days of daily backups, and opened one of
those (which presumably had worked for several days after the backup).
It opened fine, but stopped at the same record.

So I emailed a copy of that file to work on in a different location,
where Access 2K is in use, and, lo and behold, all the records were
there. I did a compact and repair, sent it back to XP, and still only
see 200 records. We've since verified that even in the most recent
version, the one that wouldn't open in XP) 2K can see all the records.

Has anyone else come across this? And, if so, is there a known strategy
I can use to rebuild the tables in XP (like delete all records, send
from 2K to text, import text into XP, etc.)?

--
Steve
--
http://www.steveclaflin.com

Note that I've always thought that access xp IS 2002, and the updates
page at MS seems to indicate that, but the person at the second site
swears it works in 2002.

By the way, the XP system doesn't show any dao40.dll; it has dao360.dll
-- as does the 2000 system, but they are different dates. Do they come
with an update, or do I get them some other way?

--
Steve
--
http://www.steveclaflin.com