When attempting to refresh a link through ODBC to a table (T_Leases) in
my SQL backend, I get an error message teling me the Jet Engine can't
find an object (A differnet table T_LockTypes in the same SQL).
I checked and am able to open, design and query the second table in
SQL. There are no relationships between these two tables. I am unable
to query the table. I tried to refresh the second table and am told the
object does not exist. I tried to remove the link to the second table
in Access but get a mesage saying the object can't be found. I tried
to run the compact/repair process but it said a use (Me!) had exclusive
use of the database. I loged out and back in and this time it allowed
me to compact/repair. I ran that several times but am still have the
same initial problem.
BACKGROUND: I run an Access Fronty end against a MS-SQL backend
runninng on a separate server. Lots of tables and I refresh them
periodically after making a change to the table in SQL. I have done
this process many times with no problems. The other tables, forms,
queries and reports (not needed the first or second table) continue to
run correctly.
my SQL backend, I get an error message teling me the Jet Engine can't
find an object (A differnet table T_LockTypes in the same SQL).
I checked and am able to open, design and query the second table in
SQL. There are no relationships between these two tables. I am unable
to query the table. I tried to refresh the second table and am told the
object does not exist. I tried to remove the link to the second table
in Access but get a mesage saying the object can't be found. I tried
to run the compact/repair process but it said a use (Me!) had exclusive
use of the database. I loged out and back in and this time it allowed
me to compact/repair. I ran that several times but am still have the
same initial problem.
BACKGROUND: I run an Access Fronty end against a MS-SQL backend
runninng on a separate server. Lots of tables and I refresh them
periodically after making a change to the table in SQL. I have done
this process many times with no problems. The other tables, forms,
queries and reports (not needed the first or second table) continue to
run correctly.