Ghost Table In Access? PLEASE HELP!

[Guest]

Is it possible to have a ghost table in Access?
Why? I have 5 tables in my Update query. 4 source tables and one
target table. I run my query and recieve an error that states "ODBC update on
linked table 'Dev_tblProduct' Failed" also "Cannot UPDATE tblProduct because
tblProductCOMPANY exists".

I do not have a table in my query with the name of "ProductCompany". However
I do have a table with that name but not in the query.It is related to the
tblProduct table I am using in my query but not in my grid.

Could this be the cause of the error? ProductCompany has nothing to do with
this query except for it being related in the table relationship window.
Thanking you all in advance.

 

[Rob Parker]

Hi Troy,

It's possible that the existing relationship between tblProduct and
tblProductCOMPANY is preventing the update, but without any details it's
impossible to be sure. It will depend on which fields are related, and how,
and (possibly) on whether you have cascading updates and/or deletes set, and
whether the fields are required fields or not; it will also depend on what
fields you are trying to update.

As a simple example, if your tblProduct has a field which requires a
matching entry in a field in tblProductCompany, and you try to change that
entry to something which does not exist in tblProductCompany, the update
will fail. Another example could be if you try to set a field which is
related to a required field to null.

You will need to carefully examine the properties and relationships for each
field you are trying to update to determine exactly where your problem lies.

HTH,

Rob

 

[Guest]

The tables are only related as a one to many. none are set with RI involved
and none are required. This is why I am lead to believe that it is at the SQL
level as the error msg states?

 

[Rob Parker]

Hi Troy,

I see you have posted this in another thread, where Doug Steele is
assisting. If the problem is at the SQL Server end, I'm afraid I can't help
there - I know next-to-nothing about that (yet!).

Good luck solving your problem,

Rob