Access 2007 opens database in "read only" mode with Vista

[Rickarita]

I developed an application in access 2000 with several vba commands. I later
upgraded to Access 2007. It worked great using XP, but I have just purchased
a computer with Vista on it. It opens the database in a "read-only" mode. In
addition, it disables my code. I have created a digital certificate and
signed the project, but it still won't recognise it. In addition, it doesn't
even offer me the option to "enable macros" when I open it. Does anyone know
how I can fix this?

 

[Pete D.]

In trust center check, section message bar, turn on Show the message
bar...has been blocked

 

[Rickarita]

Pete, thanks for the response, but this was not the problem. What I have
since figured out is that Vista does not like my ap in program files. If I
but it elsewhere, it functions normally. However, I will have to re-write a
bunch of code that refers to C:\program files\SSM. Oh well, at least I
figured this much out.

 

[Pete D.]

Glad you figured it out and thanks for posting back. Pete D.

 

[Tony Toews [MVP]]

Pete, thanks for the response, but this was not the problem. What I have
since figured out is that Vista does not like my ap in program files. If I
but it elsewhere, it functions normally. However, I will have to re-write a
bunch of code that refers to C:\program files\SSM. Oh well, at least I
figured this much out.

Yes, you should not be placing an MDB, MDE, ACCDB or ACCDE in the
Program Files folder as you have found out. That is read only access
for users.

The best location would very likely be the AppData folder. You can
use an API call to determine the location of that folder. However
this can be troublesome some depending on how you install the app to
the users PC.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

 

[David W. Fenton]

Yes, you should not be placing an MDB, MDE, ACCDB or ACCDE in the
Program Files folder as you have found out. That is read only
access for users.

Well, unless you give the users group full control of that folder.

 

[Tony Toews [MVP]]

Well, unless you give the users group full control of that folder.

No IT department would give their users this level of permission.
Nor should they.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

 

[David W. Fenton]

No IT department would give their users this level of permission.
Nor should they.

On one single folder? I didn't specify, but what I meant was full
control on the folder where you Access app is stored, not on the
programs folder.

And not all companies have an IT department, in fact.

 

[Tony Toews [MVP]]

On one single folder? I didn't specify, but what I meant was full
control on the folder where you Access app is stored, not on the
programs folder.

PITA to administer for individual users.

And not all companies have an IT department, in fact.

True enough.

Still those aren't, to me, good enough reasons to break the rules when
we don't need to.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

 

[David W. Fenton]

PITA to administer for individual users.

I'm not saying it isn't, nor that it's a recommended setup. I'm only
saying that it *can* be done (your original post seemed to me to
imply that it could *not* be done at all).

True enough.

Still those aren't, to me, good enough reasons to break the rules
when we don't need to.

The reason why some of my clients break the rule is that the setup
dates back to the days of Win9x, and it works for them.

I wouldn't set it up that way now, of course, but it's not such a
big deal to continue to support it now.