rocord sometimes comes up as ###### ######

[sirkenj]

I have a pretty complex set of tables that have pretty complex relationships, so this one may not be real easy to solve, but one can hope!

Every now and then (translation: I don't know what's causing this to happen) when I open my database, the "main" table that other relationships stem from will contain a record with either just ###### signs in every field, or other jumbled characters. Where should I start the diagnosis of this problem, and what could some of the causes be?

I have a feeling it may be from:
1. Database is split, right now both front-end and backend are on servers.
2. Two people having the same application opened, with different records???? This one is interesting to me. If I have one database with a form (frm1) which contains a text box whose control source is set to the current user, how does access handle it if that same database is opened by two different users? Is a copy of the database run on each machine? I can see where this situation could create some issues?
3. Some other record locking issue?
4. Improper shutdown / compter locked up while DB is running?

Any help will be GREATLY appreciated!!!!!

 

[johnnymac43]

In my experience this usually means some form of data corruption. It happens when corrupt data is imported from a .DBF file and is not properly handled by Access. The 'random' display of ####### occurs when the user navigates down the table past the corrupt record.

HTH

John

 

[dvannoy]

use JetComp.EXE to fix your table..then you can delete the records marked with the ###

 

[johnnymac43]

Hello sirkenj! Are you still out there?

Any help will be GREATLY appreciated!!!!!

Have the replies to date helped? Just wondering!

John

 

[sirkenj]

Yes, and no. The issue isn't so much fixing the the problem (fixing the record itself) as trying to figure out why it happens in the first place. Once this happens, the data is lost, a compact / repair, or using JetComp doesn't actually fix the record.

This seems to happen to only one record at a time, I have never seen duplicates, and strangely the only fields not affected once the record is corrupted are date fields. All other fields (text / number) are displayed as: û‹ﰂb㗾㈷