Corrupt records in converted AccessXP database

[AlanKW]

I've recently upgraded an Access97 database into AccessXP. Since then, I've had corrupted records every few days. When looking at the table; The first time, the record contained foreign characters. The second time, every field had a #error in it. This time, I couldnt view the table. Got an invalid Arguement when I tried to view, export, etc.. After kicking everyone out then deleting the LDB file, did a compact/Repair which then put a record to all ##### which I was able to delete. I had to delete the LDB file as there was a hook on the LDB from <machine name>\\SMSCliSvcAcct Usually, I see <DomainName>\<userLogon>

I am trying to appeal to the users with help on noticing anything unusual. I am at a loss with things to try to prevent this. Has anyone else experienced issues like this? Should I make a new MDB and copy all objects over?

 

[Zaichik123]

You may need to update service pack info. Downloadable from the Microsoft website...

 

[AlanKW]

My apologies - It is not AccessXP, but Access 2003 (but in the 2002-2003 database format)

 

[AlanKW]

Another corrupt record.

Gibberish characters in some text fields, completely insane numbers in lookup fields (150994944 being stored in a field where the maximum number stored under normal use would be 247) and a #error in a memo field.

If I try to delete the record in the table, I get a "The Search Key was not found in any record" and if I click in the field that has a #error, I get an "Invalid Arguement"

the CSR who entered the record doesnt recall anything weird happening when she entered it.

 

[AlanKW]

4 more corrupt records in last 2 days. This morning I hade to make a new table and copy non-corrupt records to the new table. At that point, I increased the # of idexed fields from one to 3 (The original one, the Autonumbered field; Customers last name; Customer ID#) Then this afternoon another corrupt record that prevented me from looking at the table in data-sheet view, but was changed to all #### after a compact repair.

Access2003 MDB on an NT4 Server with users using Access2003 Runtime

Any thoughts onto whats causing the corrupt records? I'm ready to listen to anything as I'm on vaca next week and would not like to leave this with my boss or Local IT.

 

[willir]

Alan

Besides the upgrade from Access 97 to a 2003 server, did you make any other changes -- say move from running the database locally, and not across the LAN to the server?

Also, I think you need to change the record locking on the server to pesimistic. Bascially, the default configuration of a servers to cache writes and then only write to disk when the cache is full. Makes the system faster if writing text files -- BUT PLAYS HAVIC with databases including messaging. Various clients also are set to cache writes.

Why are cache writes undesirable with a database? If the server caches 5 updates to the same table that uses autonumber, because the autonumber has not been updated, each of the five updates grab the same number.

Richard

 

[AlanKW]

Sorry for the delayed response. I was out longer than anticipated...

We updated all of Office to 2003 including Outlook. Something that I've noticed is that Outlook 2003 is behaving like a dial-up instead of LAN from older versions. What I mean by that is that every minute or so, It reaches out to the Exchange Server (Not upgraded) to look for new messages. Multiply that traffic by ~70 users... My personal (non-IT) thoughts are that its slowing down the network.

Before the upgrade, the database was split for a few test users, but a majority was working directly off the back-end. After the upgrade, all users were using the Front-end/back-end process.

As far as record locking - Access 2003 does not use the Optimistic/pessimistic terminology in Tools, Options, Advanced in default Record Locking. There are 3 options “No Locks” (selected), “All records”, “Edited record”. Below that there is a check box for “Open Database using record level locking”

Since this is in a call-center environment, I do not want a memory “page” blocked as CSRs would be entering in adjacent records at any given time.

Does this help explain the environment better?
-alan