Corrupt database

[Hello1]

Strange things happening with one of my .mdb files.
In one table, there are records which cant contain a Null value but they do and have ### instead real value (screenshoot in attachment)
I replaced the database with a backup one but then again same happened when the same records had to be added.

Im posting in attachment the structure of the table and the other related table as some of the data in it. Also I will post what the MSysCompactError table contains.

[theDBguy]

Can't remember if the recent issue with the Windows Updates affect MDBs, but maybe they do. Have you looked into it yet? For example, what version of Windows are you using and what build?

[Hello1]

Edition: Windows 10 Pro
Version: 1903
OS build: 18362.476

To be honest I have no idea, the database is not at my PC tho.
Which issue do you exactly mean? Could you provide a link about it?

Thanks

Btw office is the 2007 one

[theDBguy]

Again, not sure it this affects your, but you could start here to see what I meant.

[Hello1]

I read it however, Im not sure that it is the exact same problem, the symptoms seem different. I can still use and open the database.
Any way to try and recover the lost records?

[theDBguy]

Originally Posted by Hello1

I read it however, Im not sure that it is the exact same problem, the symptoms seem different. I can still use and open the database.
Any way to try and recover the lost records?

That's what I was trying to say earlier. I wasn't sure if you're affected, but it couldn't hurt to check if the recommended solutions work for your situation too. As for recovering "lost" records, only if you have a backup copy (especially after a C&R has been performed already).

[Hello1]

So I suppose not worth trying any mdb repair/recovery software?

[theDBguy]

Originally Posted by Hello1

So I suppose not worth trying any mdb repair/recovery software?

That depends on the potential return on investment (ROI). How important are the lost data and how much are you willing to pay to "maybe" recover it? If you have a good backup plan, you should only lose a few of them, and maybe make it easier to recover the lost records by simply re-entering them again. Just my 2 cents...

[Hello1]

Alright, there are some backups and yes I guess I will use it but how to prevent this from happening again?
It's strange that it happened on a backup database too.
I'm not sure if it could be an virus infection, but the windows defender didn't find anything suspicious on the PC. Maybe migrating to SQL Server but before doing so I would like to find the cause and see how else to prevent it.

[isladogs]

Your Stav…. Table doesn't have a primary key though you do have an autonumber field.
The fact that several of those are null does indeed indicate corruption.
As already stated you will need to delete those corrupt records then make your autunumber fields the PK.
Check whether the FK field allows fulls. It shouldn't for RI to work.

As for the cause of the corruption, are multiple users sharing the database?

Out of interest, what do you see if you widen the columns for the 2 fields showing #######?

[Hello1]

As already stated you will need to delete those corrupt records then make your autunumber fields the PK.
Check whether the FK field allows fulls. It shouldn't for RI to work.

Would it be better just to take the backup database?

As for the cause of the corruption, are multiple users sharing the database?

As Im aware only one user is using the database, locally.

Out of interest, what do you see if you widen the columns for the 2 fields showing #######?

Nothing it stays as it is, #####

[isladogs]

Either use your backup or delete the corrupted records - whichever means fewer records are lost.
Check whether you have Automatic Compact On Close ticked in Access Options.
If so un-tick it as that can cause corruption