"id" is not index on this table

[yamus]

Hello
I don't know how it happened. But when i open the database file i get the error messsage saying ' "id" is not index on this table '
Can anyone please help me

 

[isladogs]

Hi
I'm not sure what version of Access you're using but its an error I haven't seen for many years.
The good news is that its fixable. See Fixing Corruption: AOIndex is not an index in this table: Microsoft Access Tips and Tricks from DataGnostics

 

[yamus]

Hi
I'm not sure what version of Access you're using but its an error I haven't seen for many years.
The good news is that its fixable. See Fixing Corruption: AOIndex is not an index in this table: Microsoft Access Tips and Tricks from DataGnostics

i am using office 2013

 

[isladogs]

The fix should still work. Try it and report back...

 

[yamus]

The fix should still work. Try it and report back...

There was an access app provided by Datagnostics.com to fix corrupted databases. i downloaded it and extracted as mentionned. But, when I launched it and clicked on 'I agree on conditions' button, it closed.
It's worth mentionning that i noticed the app code is written in an old access version. I made a modification adding 'ptrSafe' to the 3 'declare' statements in 'basFileOpenSave' module

 

[isladogs]

Ok so you're using 64-bit Access 2013 which you hadn't mentioned before.
So now you've converted it for 64-bit, were you able to follow the website instructions and apply the fix?

 

[yamus]

Ok so you're using 64-bit Access 2013 which you hadn't mentioned before.
So now you've converted it for 64-bit, were you able to follow the website instructions and apply the fix?

I am following instructions but as i told you earlier, when i click 'i agree' button, the app(and the access file) closes

 

[isladogs]

The old File Open code would need further changes and even then may not run in 64-bit.
However you could get rid of that entire module and replace it with code using file scripting object (FSO) to select and open your database programmatically.
However I would first check whether you have the hidden system table MSysAccessObjects which this utility is designed to fix

 

[yamus]

The old File Open code would need further changes and even then may not run in 64-bit.
However you could get rid of that entire module and replace it with code using file scripting object (FSO) to select and open your database programmatically.
However I would first check whether you have the hidden system table MSysAccessObjects which this utility is designed to fix

Ooops. I think deleted that table by mistake.
Would that be a problem?

 

[isladogs]

Many system tables cannot be edited or deleted. Even if you can do so, you should NEVER delete a system table.
Having said that, the MSysAccessObjects table was only used in old databases created between A97 & A2003.
So unless your dB was created in an old version you wouldn't have that table...which is why I asked...and why this error is rarely seen these days

No point using that utility though...

If the error still occurs, make a backup ...just in case ... then import all objects except system tables into a new 'clean' database.
New system tables will automatically get created

 

[yamus]

Many system tables cannot be edited or deleted. Even if you can do so, you should NEVER delete a system table.
Having said that, the MSysAccessObjects table was only used in old databases created between A97 & A2003.
So unless your dB was created in an old version you wouldn't have that table...which is why I asked...and why this error is rarely seen these days

No point using that utility though...

If the error still occurs, make a backup ...just in case ... then import all objects except system tables into a new 'clean' database.
New system tables will automatically get created

Ok i see.
Well, i already made the imports you suggetsed.
I managed to import tables, queries, forms and Class Objects. One problem left. I can not import modules. The same error keeps showing up
Is there a way to fix this problem?

 

[isladogs]

Sounds like the code is corrupted. Try DECOMPILING your project. See Decompile and Compact Your Microsoft Access Database to Improve Performance and Fix Corruption (fmsinc.com)
Then try and import the modules. If necessary, try importing the modules one at a time -there may be an issue in one module only
If even that fails, hold down the shift key as you open your dB and you could then try exporting each of the modules as text files (with a .bas suffix) ...then import those into the VBE of the new database.

 

[yamus]

Sounds like the code is corrupted. Try DECOMPILING your project. See Decompile and Compact Your Microsoft Access Database to Improve Performance and Fix Corruption (fmsinc.com)
Then try and import the modules. If necessary, try importing the modules one at a time -there may be an issue in one module only
If even that fails, hold down the shift key as you open your dB and you could then try exporting each of the modules as text files (with a .bas suffix) ...then import those into the VBE of the new database.

Hello
Nothing seems to work
I remade the missing module since most of code within is open source
Thank you anyway

 

[Cronk]

Try creating a new blank database and importing everything from the problematic db.