By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
446,392 Members | 1,556 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 446,392 IT Pros & Developers. It's quick & easy.

Shared access database "Object Invalid or No Longer Set"

P: 1
I have recently posted a new access database and its oracle tables onto a shared folder for various users. It is a search database and me and a few other users are able to pull from the file and use it perfectly. But, when other users pull from the shared folder they suffer from dragging performance and then the fields within the forms error to "#Name?" and an "Object Invalid or No Longer Set" error button comes up.

Seeing as though we are all using the same database, I have tried to make sure the users with the error are using the correct, updated copy of the database. I have tried running an oracle driver update to make sure they have the correct mapping. I created this file on XP and it's access 2003. The users also have access 03. I feel like it shouldn't be a coding issue seeing as though the database itself works on some computers and not on others. I'm leaning towards a Microsoft Jet database situation? I don't believe it is a memory situation either, as that might explain the slow performance on some users databases, but not the errors. I am hoping to see if anyone has an idea as to why the database works perfectly on some computers and errors out after a couple searches on others. Thanks!
Aug 31 '07 #1
Share this Question
Share on Google+
3 Replies


VBPhilly
P: 95
I have recently posted a new access database and its oracle tables onto a shared folder for various users. It is a search database and me and a few other users are able to pull from the file and use it perfectly. But, when other users pull from the shared folder they suffer from dragging performance and then the fields within the forms error to "#Name?" and an "Object Invalid or No Longer Set" error button comes up.

Seeing as though we are all using the same database, I have tried to make sure the users with the error are using the correct, updated copy of the database. I have tried running an oracle driver update to make sure they have the correct mapping. I created this file on XP and it's access 2003. The users also have access 03. I feel like it shouldn't be a coding issue seeing as though the database itself works on some computers and not on others. I'm leaning towards a Microsoft Jet database situation? I don't believe it is a memory situation either, as that might explain the slow performance on some users databases, but not the errors. I am hoping to see if anyone has an idea as to why the database works perfectly on some computers and errors out after a couple searches on others. Thanks!
This might be a shot in the dark, but have your tried reparing?
Also, how big is the mdb. anything over 1GB makes problems. Try shrinking the mdb in that case.
Aug 31 '07 #2

JConsulting
Expert 100+
P: 603
I have recently posted a new access database and its oracle tables onto a shared folder for various users. It is a search database and me and a few other users are able to pull from the file and use it perfectly. But, when other users pull from the shared folder they suffer from dragging performance and then the fields within the forms error to "#Name?" and an "Object Invalid or No Longer Set" error button comes up.

Seeing as though we are all using the same database, I have tried to make sure the users with the error are using the correct, updated copy of the database. I have tried running an oracle driver update to make sure they have the correct mapping. I created this file on XP and it's access 2003. The users also have access 03. I feel like it shouldn't be a coding issue seeing as though the database itself works on some computers and not on others. I'm leaning towards a Microsoft Jet database situation? I don't believe it is a memory situation either, as that might explain the slow performance on some users databases, but not the errors. I am hoping to see if anyone has an idea as to why the database works perfectly on some computers and errors out after a couple searches on others. Thanks!
This could very well be a permissions issue also. It could be something as abstract as the user's virus protection. It could be a timeout issue. Without knowing more about your database design, this one is very difficult to try to offer any kind of concrete and intelligent diagnisos.
J
Sep 1 '07 #3

Jim Doherty
Expert 100+
P: 897
I have recently posted a new access database and its oracle tables onto a shared folder for various users. It is a search database and me and a few other users are able to pull from the file and use it perfectly. But, when other users pull from the shared folder they suffer from dragging performance and then the fields within the forms error to "#Name?" and an "Object Invalid or No Longer Set" error button comes up.

Seeing as though we are all using the same database, I have tried to make sure the users with the error are using the correct, updated copy of the database. I have tried running an oracle driver update to make sure they have the correct mapping. I created this file on XP and it's access 2003. The users also have access 03. I feel like it shouldn't be a coding issue seeing as though the database itself works on some computers and not on others. I'm leaning towards a Microsoft Jet database situation? I don't believe it is a memory situation either, as that might explain the slow performance on some users databases, but not the errors. I am hoping to see if anyone has an idea as to why the database works perfectly on some computers and errors out after a couple searches on others. Thanks!

Are they sharing the SAME database ie the one file on a standard pc acting as a server, or is it a proper server.? How many concurrent users are there?

My advice FWIW is give each user their own copy db working directly of their client machine and deal with any mdb distribution issues via logon batch file (if authenticating against a domain) or whatever other method suits you.

They can then deal with compaction of their own frontend database copies, have their own particularised features if necessary, you then have the advantage of isolating any future connectivity issues per seat rather than having no start point at all and maybe not knowing where to start with issues such as this merely because everyone accesses the one MDB file across a busy network.

To test this out you might want to try running the db from the problematic client pc's.you are using the oracle driver which if so you'd have to ensure this odbc driver was also obviously on the problem pc etc etc. The extra effort may sound painful but it is necessary to isolate and resolve the problem. On certain occasions ie mega busy network, slow NIC cards and so on ended up using CITRIX to resolve it.

Wishing you luck

Jim
Sep 1 '07 #4

Post your reply

Sign in to post your reply or Sign up for a free account.