"invalid database object reference" depending on deference versions of ms access?
Hi to every one
I have "invalid database object reference"
It works properly at some devices only.
I have test it on these devices:
Device work properly
--------------------------
Disk top with windows 7 and office 2010 OK
Disk top with windows XP and office 2003 OK
Lap top with windows XP and office 2003/2007 OK with the two offices version
Lap top with windows 7 and office 2010 "invalid database object reference"
Lap top with windows 7 and office 2010 "invalid database object reference"
Lap top with windows 7 and office 2007 "invalid database object reference"
You can see the reference I have in the attached file.
Please help!
1.JPG
2.JPG
I have "invalid database object reference"
It works properly at some devices only.
I have test it on these devices:
Device work properly
--------------------------
Disk top with windows 7 and office 2010 OK
Disk top with windows XP and office 2003 OK
Lap top with windows XP and office 2003/2007 OK with the two offices version
Lap top with windows 7 and office 2010 "invalid database object reference"
Lap top with windows 7 and office 2010 "invalid database object reference"
Lap top with windows 7 and office 2007 "invalid database object reference"
You can see the reference I have in the attached file.
Please help!
1.JPG
2.JPG
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Humm ... so, problem solved?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I had a similar issue with one of my databases. The issue would only arise when 'Compact on Close" was set. In my case this error was due to one of my linked tables that was linked using a UNC path, while all the others used a mapped drive letter.
I have not tracked down the root of why this is an issue, but removing the UNC linked table before the database closes did resolve this issue for me.
I hope this helps!
Jacob
I have not tracked down the root of why this is an issue, but removing the UNC linked table before the database closes did resolve this issue for me.
I hope this helps!
Jacob
ASKER
"one of my linked tables that was linked using a UNC path"
i am sorry, but what is "UNC path linking" please?
i am sorry, but what is "UNC path linking" please?
Guess I am confused. Does
"But when I "compact and repair" the database at the same devices i need to play it on, it seems to be work properly."
... it is now working ?
mx
"But when I "compact and repair" the database at the same devices i need to play it on, it seems to be work properly."
... it is now working ?
mx
ASKER
yes. but it needs from me to "compact and repair" at each 2010 office device.
"i am sorry, but what is "UNC path linking" please?"
It means basically not using any Mapped Drive letters, but instead the Full Network Path to a Server where the back end folder is located.
My Network Places >> Entire Network >> Microsoft Windows Network >> SomeWorkgroupName >>
SomeFolderName >> SomeBackEndDbName
mx
It means basically not using any Mapped Drive letters, but instead the Full Network Path to a Server where the back end folder is located.
My Network Places >> Entire Network >> Microsoft Windows Network >> SomeWorkgroupName >>
SomeFolderName >> SomeBackEndDbName
mx
ASKER
thank you
in case of jwilberd:
i have all of my tables are linked to Back end DB except one table is included in the same front end mdb file. and i name it UsysMytablename for security issue.
i'll try to transfer it to the Back end and see what i 'll get!
in case of jwilberd:
i have all of my tables are linked to Back end DB except one table is included in the same front end mdb file. and i name it UsysMytablename for security issue.
i'll try to transfer it to the Back end and see what i 'll get!
ASKER
thanks a lot
and very sorry for late
and very sorry for late
ASKER
I do change the references as you mention, but nothing happen. i get the same problems.
But when I "compact and repair" the database at the same devices i need to play it on, it seems to be work properly. I test it at two of the devices not working before. And it's work good now?!!!