"The Microsoft Jet database engine could not find

[INFOS]

I have a very strange problem with Microsoft Access. I work with this tool for six years and I did not have something like this ever.
This is the situation:
I have 8 computers - same configurations - AsusP4P800, P-4 3.0GhZ, 512MB, - same windows - XP SP2 - same Office - XP SP3.
On two computers I have error. I have try to reinstall offfice, reinstall windows...I suspected on Jet40 but it has latest service pack allready.
What is the error: Application has tables linked to Access database. When I open the application and I open (any) LINKED table there is
some crazy data in the table (mostly all the columns contains data from the first column). When I close the linkedtable
and open it again everything is ok - also all the other linked tables are ok. Error is happening only first time that linked
table is opened in access file. Also I recieve error when I try to delete link tables (if I did not open any linked table in
application once). When I try to delete it first time I recieve this error message:
"Circular reference caused alias "Expr1000" in query definition's SELECT list."
Then I press OK and try to delete it again - after I recieve this error messages:
"The Microsoft Jet database engine could not find the object "szRelationship". Make sure
the object exists and that you spell its name and the path correctly"
I just have to open any linked table once and everything is ok - I can delete linked table and work normally till next
time I open application again. DO YOU KNOW WHY IS THIS HAPPENING?

 

[The_Doc_Man]

The question is how the linkages are defined, perhaps.

If you map a drive to a letter, verify that the same mappings are used for all systems with respect to where your DB resides.

If you map to a universal reference (\\host\path...\file) this is not the culprit.

I am also intrigued by the error message:

"Circular reference caused alias "Expr1000" in query definition's SELECT list."

It is almost as though something is being left behind in a cache that should not be there, and when you try to delete your linked table, something dependent on that table is responding to a leftover environmental definition. Which is sorta bizarre 'cause that's not supposed to happen with Windows.

 

[INFOS]

strange problem with linked tables

It is not a problem with maping. I can make one access file with one table
and other access file with one linked table to the first one. And error I
have explained happens. If I make the same thing on the other computer
(same windows, same office, same configuration) - everything is ok. If I
copy two files made on the "bad" computer they work properly on the other
one.

 

[The_Doc_Man]

I hope we are talking about a network-accessed .MDB file.

Verify that the computer / user that is having the problem is properly defined as a member of the group having permissions to the folder with the Access .MDB file. (Or that the individual user has the required permissions.) You might need the file-server administrator to reset them for you.

If this is a local machine problem (i.e. fails when you create the .MDB files on the same machine you use for accessing them) then you've got me stumped.

If you have a way to run some of the Symantec or other registry tools to document your system settings, it would be a good idea to compare the registries for the machines that work and that don't work.

ALSO - this thought just occurred to me... WinXP SP2 turns on the flags that require digitally-signed modules. Verify signatures and verify that the systems having those signatures have the SAME set of signatures.

ALSO - if you have enabled Kerberos authentication in your domain, verify that the time-of-day clock on your errant system is set to the same time as the other systems - and more specifically, to the system time of the machine acting as your Kerberos ticket controller.

 

[WindSailor]

"Circular reference caused alias "Expr1000" in query definition's SELECT list."

It has been a over a year since I have seen this and I haven't used Access in a while so bear with me...

What I can remember what can cause this problem is that there is a single column in a query that is repeated more than once, and I would assume that it is used in an expression and this original column (name?) has a relationship. By default Access will rename the repeated column in the query "Expr1000" on so on. I would go back and look for repeated columns etc. and check your code.

Hope this helps.

 

[INFOS]

There is no query at all - just one linked table with a problem.

 

[INFOS]

Reply For The Docman

Error is happening on a single computer. I have one access file with a table and other file with a linked table (to the first one) and they are in the same directory.
I have made some testing on the computer:
I have try other processor - same error occurs
I have try other memory - same error occurs
I have try Office 2000 - same error occurs
I have try Office 2003 - same error occurs
I have try to reinstal windows XP - same error occurs
I have try WINDOWS 98 - EVERYTHING IS OK (with the same office)
Then I have try Windows XP again and same error occurs.
But I can't work in Win98 - I need WinXP.