Rogue table?

[Les Isaacs]

Hello

This is the weirdest problem I've had in a long time: interesting - but exasperating:banghead:

I am being prevented from adding a new record to table [x confirmed] - when I try to do so I get a message that a related record is required in table [practicesBAD]. The table [practicesBAD] was created over a year ago as a copy of table [practices], when I had some problems with the table [practices]. The problems were sorted, and I deleted the table [practicesBAD]. This was all over a year ago, and since then thousands of record have been added to table [x confirmed] without a problem.

Table [x confirmed] has a field [prac name] which is related to the key field [practice] in table [practices], with referential integrity enforced.

Today, we can add records to [x confirmed] with any of the values of [prac name] from table [practices] except one - when I get the message that a related record is required in table [practicesBAD]. But I cannot find any evidence that [practicesBAD] still exists - either in the list of tables in the object browser, or in the Relationships window, or in the database documenter

I have tried adding a record with the suspect [prac name] value directly into the table (rather than via the normal INSERT method), but this makes no difference.

Does anyone have any ideas
Thanks in advance for any help.
Les

 

[Les Isaacs]

Hi Pat
Many thanks for your reply.
I had tried 'show all' on the relationships window, to no avail. I have though found the answer I hesitate to give it here, because it's a bit embarrassing, but I suppose I should: the table still existed in the backend database I can't believe I had forgotten to check this, but it didn't occur to me that 'show all' would fail to show all the relationships - i.e. including any that were to tables no longer linked to the frontend database.
So, problem sorted, lesson learnt, and thanks again for your help - I'll bear in mind what you said about Name Auto Correct.
Les