...a couple of days ago the companies access db crashed.
when i went to look at the tables the message
["" is not a unique identifier] was displayed.
i tried for hours using all the tricks i could think of to get it to open, but in the end gave up and bought a program called advanced access repair which managed to get the tables back.
I copied the main table into a new 'shell' and thought the nightmare was over.
However, i realise all is not well because when a new record is created the code that puts 0 in the fields on a form does not work and the code that works VAT out only kicks in if you save the record and go back into it.
now i started blaming the code/forms etc, but if i replace the table with a previous backups it works fine.
both tables look the same [design wise], they are called the same i cant see any difference [apart from the content] which shouldnt matter because this is a New record.
this is really bugging me.
im using access 97.
any ideas welcome
cheers MG
backups will save your soul
when i went to look at the tables the message
["" is not a unique identifier] was displayed.
i tried for hours using all the tricks i could think of to get it to open, but in the end gave up and bought a program called advanced access repair which managed to get the tables back.
I copied the main table into a new 'shell' and thought the nightmare was over.
However, i realise all is not well because when a new record is created the code that puts 0 in the fields on a form does not work and the code that works VAT out only kicks in if you save the record and go back into it.
now i started blaming the code/forms etc, but if i replace the table with a previous backups it works fine.
both tables look the same [design wise], they are called the same i cant see any difference [apart from the content] which shouldnt matter because this is a New record.
this is really bugging me.
im using access 97.
any ideas welcome
cheers MG
backups will save your soul