Please Help!!

[golfinray]

Somehow a user has deleted a record in a keyed field in a form. Two tables
have a one-to-one relationship with project # as the key in both. Now both
show on the project # that should be there, #deleted# in every field. I have
tried deleting the record, making a query to remove the record, going to the
BE and turning off the keys, removing the indexes, removing the
relationships, deleting in the BE and nothing gets rid of that record. I
deleted in the BE and re-linked, deleted the record then added that project
number back in, nothing works. Help Please. Thanks!!!!!

 

[Daniel Pineault]

Perform a compact and repair on the back-end.
--
Hope this helps,

Daniel Pineault
http://www.cardaconsultants.com/
For Access Tips and Examples: http://www.devhut.net
Please rate this post using the vote buttons if it was helpful.

 

[Jeff Boyce]

Are you looking for a way to prevent this from happening again...?

Regards

Jeff Boyce
Microsoft Access MVP

--
Disclaimer: This author may have received products and services mentioned
in this post. Mention and/or description of a product or service herein
does not constitute endorsement thereof.

Any code or pseudocode included in this post is offered "as is", with no
guarantee as to suitability.

You can thank the FTC of the USA for making this disclaimer
possible/necessary.

 

[golfinray]

YES!!!! Thanks

 

[Jeff Boyce]

First, if you provide a user interface, the users don't need to muck about
directly in the tables, which they can easily confuse with spreadsheets.

Second, if you have them interact with the data through a form, you can use
the events connected with the form to prevent them from deleting records.
Check the form's BeforeDelete event, and in a procedure there, "cancel" the
delete. You'll probably also want to give them a message informing them
that they are not allowed to delete records.

(finally, talk with them. Find out why they might want to and/or feel they
had to delete a record. Maybe they have a legitimate need to?!)

Good luck!

Regards

Jeff Boyce
Microsoft Access MVP

--
Disclaimer: This author may have received products and services mentioned
in this post. Mention and/or description of a product or service herein
does not constitute endorsement thereof.

Any code or pseudocode included in this post is offered "as is", with no
guarantee as to suitability.

You can thank the FTC of the USA for making this disclaimer
possible/necessary.