robjones23
Registered User.
- Local time
- Today, 22:06
- Joined
- Dec 16, 2004
- Messages
- 66
Hi all,
Our company is currently rolling out an SP2 update to all of our PC's and this problem has reared its head on all of the updated PC's so far.
Basically when someone opens a database from a shared drive, they get an error stating that the file was made by an unknown publisher (seems to be a security warning), they click ok and then can open the file fine.
However, once someone is in the database, if anyone else tries to open it on an SP2 machine, nothing happens, the double click the file and it refuses to open. If they open Access, then click file>open and navigate to the file, they can open it. They just can't double click the file.
People using the SP1 machines can open the database with no problems whether someone is already in the file or not.
I'm guessing this is something to dow tih the SP2 security measures.
To try to sort it out, I made myself a self signed digital ceritificate and signed my macros, thinking that once the macros were signed, it would then realise who had published the file.
The only thing this does is brings up a second notice (after the initial publisher message) which gives you the option to trust content from my signature. Once this has been done once, there's no need to keep trusting it but the publisher message still comes up.
I went into the database properties and under the custom tab changed the "publisher" value to my name "Rob Jones". This still didn't work and when the database is opened it still says it's an unknown publisher.
Does anyone know how to either turn off this check or publish a database?? I've tried google / MS but can't find anything on the subject.
Cheers,
Rob.
Our company is currently rolling out an SP2 update to all of our PC's and this problem has reared its head on all of the updated PC's so far.
Basically when someone opens a database from a shared drive, they get an error stating that the file was made by an unknown publisher (seems to be a security warning), they click ok and then can open the file fine.
However, once someone is in the database, if anyone else tries to open it on an SP2 machine, nothing happens, the double click the file and it refuses to open. If they open Access, then click file>open and navigate to the file, they can open it. They just can't double click the file.
People using the SP1 machines can open the database with no problems whether someone is already in the file or not.
I'm guessing this is something to dow tih the SP2 security measures.
To try to sort it out, I made myself a self signed digital ceritificate and signed my macros, thinking that once the macros were signed, it would then realise who had published the file.
The only thing this does is brings up a second notice (after the initial publisher message) which gives you the option to trust content from my signature. Once this has been done once, there's no need to keep trusting it but the publisher message still comes up.
I went into the database properties and under the custom tab changed the "publisher" value to my name "Rob Jones". This still didn't work and when the database is opened it still says it's an unknown publisher.
Does anyone know how to either turn off this check or publish a database?? I've tried google / MS but can't find anything on the subject.
Cheers,
Rob.