Weird Issue (4 Viewers)

[SykesIT]

Hi I have a weird issue with one computer.

I have a DB on one pc and is shared with 3 other PC and works fine.

And yes I am going to split the db when I get chance. As I haven't done that before waiting.

The issue is I have a laptop that has most recent version of Office on and has the same mapped network drive to the pc with the DB, but when I open the DB I get different errors, from "DB in an inconsistent state" to Search Query error to VBA error.

If I try repair it usually corrupts the DB.

I am at a loss as to why this one machine has an issue.

Even if I copy the DB local I still get errors.

Does anybody have any suggestions?

 

[RonPaii]

Is the laptop on wifi?

 

[xavier.batlle]

Splitting databases is the main reason to avoid weird errors. I think that most of gurus here can't help you on an unsplitted database.

 

[Gasman]

Also if you split it, you remove the chance of corrupting the data from the code?

 

[GPGeorge]

"The issue is I have a laptop that has most recent version of Office on and has the same mapped network drive to the pc with the DB..."

Did you designate the folder where the accdb is located on your own computer as a Trusted Location for this laptop's installation of Access?

 

[SykesIT]

Is the laptop on wifi?

No hard wired

 

[SykesIT]

"The issue is I have a laptop that has most recent version of Office on and has the same mapped network drive to the pc with the DB..."

Did you designate the folder where the accdb is located on your own computer as a Trusted Location for this laptop's installation of Access?

It usually pops up and asks you to give access rights but hasn't.

I haven't done anything on other pc for trusted locations, just on the main pc which hosts the db.

 

[GPGeorge]

I'm sorry, but I don't know what this means, "...asks you to give access rights but hasn't." Please explain, or better yet, show the actual message as a screenshot. I suspect, though, that it does refer to the problem of not having designated Trusted Locations.

I'm going to refer to the computer where the accdb is located as the Host PC.

If the other PC doesn't have the folder where the accdb is located on the Host PC designated as a Trusted Location, Access will block code in that accdb from running. That may or may not be part of the current problem with other errors, but it would raise a warning about using the accdb that might be similar to your "give access rights" message.

Someone needs to open Access on the other computer and designate the folder on the host PC as a Trusted Location for that other computer to use. If that also reduces the number of errors, you'll be on the right track.

Another possibility is that the accdb uses References that are available on the Host PC, but not on the other computer. That would raise different errors when code tries to run.

Please check out those things and then see if the problem is resolved, or partially resolved. Let us know how it goes.

 

[cheekybuddha]

And yes I am going to split the db when I get chance. As I haven't done that before waiting.

Don't wait too long!

99 times out of 100, multiple users sharing/accessing the same copy of an Access db will lead to errors and eventual corruption.

 

[The_Doc_Man]

Your problem sounds like an update is occurring. To share a DB in the way you appear to be doing, you need every PC to have a "local" copy of Access. More specifically, Access MUST be installed on each of the individual computers. But here is the 'gotcha' - what are the versions of Access on the three machines that seem well-behaved and on the machine that you say is using the newer version?

You can find version numbers by opening Access (to any valid DB) and then, from the ribbon, use Form >> Account >> About and the version info is in bold print at the top of that page that pops up.

 

[SykesIT]

I'm sorry, but I don't know what this means, "...asks you to give access rights but hasn't." Please explain, or better yet, show the actual message as a screenshot. I suspect, though, that it does refer to the problem of not having designated Trusted Locations.

I'm going to refer to the computer where the accdb is located as the Host PC.

If the other PC doesn't have the folder where the accdb is located on the Host PC designated as a Trusted Location, Access will block code in that accdb from running. That may or may not be part of the current problem with other errors, but it would raise a warning about using the accdb that might be similar to your "give access rights" message.

Someone needs to open Access on the other computer and designate the folder on the host PC as a Trusted Location for that other computer to use. If that also reduces the number of errors, you'll be on the right track.

Another possibility is that the accdb uses References that are available on the Host PC, but not on the other computer. That would raise different errors when code tries to run.

Please check out those things and then see if the problem is resolved, or partially resolved. Let us know how it goes.

When I say that I mean enable content message.

 

[SykesIT]

Don't wait too long!

99 times out of 100, multiple users sharing/accessing the same copy of an Access db will lead to errors and eventual corruption.

This has currently been running since May 2024 no issues apart from this laptop.

 

[Gasman]

This has currently been running since May 2024 no issues apart from this laptop.

So you have been really, really, really lucky.

 

[GPGeorge]

When I say that I mean enable content message.

"Enable content message"?
That does mean that you have not yet designated the folder where the accdb resides on the Host PC as a Trusted Location for the laptop. If you need help doing that, let us know.

Until you do that, there will be problems running it from the laptop as it is now set up.

As others have pointed out, though, the proper solution is to split the accdb now. Copy the Front End to each of the computers used by your users. A separate copy on each such computer. No more sharing a single accdb across the network. Only the Back End is shared.

 

[SykesIT]

"Enable content message"?
That does mean that you have not yet designated the folder where the accdb resides on the Host PC as a Trusted Location for the laptop. If you need help doing that, let us know.

Until you do that, there will be problems running it from the laptop as it is now set up.

As others have pointed out, though, the proper solution is to split the accdb now. Copy the Front End to each of the computers used by your users. A separate copy on each such computer. No more sharing a single accdb across the network. Only the Back End is shared.

 

[SykesIT]

Checked and the path is already trusted and it's the UNC path not the mapped drive path.

 

[GPGeorge]

Checked and the path is already trusted and it's the UNC path not the mapped drive path.

So either the message is referring to something else and you would help us get to the bottom of this by showing us an actual screenshot of the error message, or there is still a problem in the configuration of the Trusted Locations as they are defined on the Laptop which has the problem.

Either way, splitting the database and installing a copy of the FE on the Laptop is definitely a good plan.

 

[SykesIT]

So either the message is referring to something else and you would help us get to the bottom of this by showing us an actual screenshot of the error message, or there is still a problem in the configuration of the Trusted Locations as they are defined on the Laptop which has the problem.

Either way, splitting the database and installing a copy of the FE on the Laptop is definitely a good plan.

There seems to be something else going on. I have split the db as a test and on the other pc I can copy over the db that has been modified Ponting the tables to the new backend. On other pc fine copy and run and perfect. On the laptop I cant even copy the file over get error invalid signature.

 

[tvanstiphout]

> error invalid signature
Is that the EXACT error message? Please quote any error messages VERBATIM.

Do I understand correctly that the error occurs while copying the FE file (presumably using Windows Explorer)? If so, this is not an Access issue but a Windows issue.

This error?

 

[SykesIT]

> error invalid signature
Is that the EXACT error message? Please quote any error messages VERBATIM.

Do I understand correctly that the error occurs while copying the FE file (presumably using Windows Explorer)? If so, this is not an Access issue but a Windows issue.

Yes Error 0x80090006: Invalid Signature