Trusted Locations

[mdavisfps]

I'm trying to unravel a problem at another site where a user with an Access
2007 frontend linked to the backend on a file server can only read records,
but not edit them. At the Windows level, the user has full control for the
shared folder and can copy and delete .doc files to that folder.

I've spent time reading about setting Trusted Locations and
AllowNetworkLocations and had attempted to do that at that other site and
thought I had the problem fixed. When I left that site last week, the user
was able to read and write to the backend database on the shared folder. Now
it's not working again, so I was going back over to see what's changed.

Anyhow, before I went back to that other site, I thought I would look at the
settings at my local site on a Vista computer which uses an essentially
identical Access 2007 frontend and is linked to a similar backend on a
similar file server. This computer can read and write to the file server
without any problem. It can link back and forth to the server backend or to
its own local copy of the backend without any problem.

When I checked Trusted Locations on this Vista/Access 2007 computer, however,
nothing has been changed from the initial installation. The only trusted
location is the default path to the Wizards databases. Also, "Allow trusted
locations on my network" is not checked. The only change was to enable all
macros.

Questions:
Why is this computer able to read/write to a shared network folder at all
when that folder has not been added as a Trusted Location? Is there something
about Vista (with UAC off) which overrides or cancels the necessity for
specifying Trusted Locations in Access 2007? Is there some other setup option
which I'm overlooking which allows this Access 2007 database to edit records
on the server and which might account for the problems at the other site?

Any help appreciated.
Thanks,
Mark

 

[John Spencer]

As far as I know, changes to the data are not prohibited by whether or
not the data resides in a trusted folder. The trusted folder controls
whether or not VBA code can execute and which macro actions can execute.

So if the data is all in a back-end and all the code and macros are in a
front-end, then I would think that the front-end had to be in a trusted
location, but not so for the back-end.

If I am wrong, I wait correction.

'====================================================
John Spencer
Access MVP 2002-2005, 2007-2009
The Hilltop Institute
University of Maryland Baltimore County
'====================================================

 

[mdavisfps]

John,
Thanks for your response.
I'm going to hang my head and crawl away in shame ...
it was a permissions/security setting on the file server for the shared
folder.
But thank you for clarifying the Trusted Locations issue.
In fact, I removed all the trusted locations -- local and the shared network
folder -- and everything runs fine with just "enable all macros" checked. I
tried different procedures & functions and there doesn't *seem* to be any
problem running code. -- should there be?

Thanks,
Mark

As far as I know, changes to the data are not prohibited by whether or
not the data resides in a trusted folder. The trusted folder controls
whether or not VBA code can execute and which macro actions can execute.

So if the data is all in a back-end and all the code and macros are in a
front-end, then I would think that the front-end had to be in a trusted
location, but not so for the back-end.

If I am wrong, I wait correction.

'====================================================
John Spencer
Access MVP 2002-2005, 2007-2009
The Hilltop Institute
University of Maryland Baltimore County
'====================================================

I'm trying to unravel a problem at another site where a user with an Access
2007 frontend linked to the backend on a file server can only read records,

[quoted text clipped - 31 lines]

Thanks,
Mark

 

[John Spencer]

I don't know the answer to your question. I have not been using Access
2007 much - none of my users are using it at all.

I have played around with it and like some of the new features, but I
also do not like some of the new features as they make life simpler for
simple databases, but make things tougher if you use them for complex
databases that are well-designed.


'====================================================
John Spencer
Access MVP 2002-2005, 2007-2009
The Hilltop Institute
University of Maryland Baltimore County
'====================================================

John,
Thanks for your response.
I'm going to hang my head and crawl away in shame ...
it was a permissions/security setting on the file server for the shared
folder.
But thank you for clarifying the Trusted Locations issue.
In fact, I removed all the trusted locations -- local and the shared network
folder -- and everything runs fine with just "enable all macros" checked. I
tried different procedures & functions and there doesn't *seem* to be any
problem running code. -- should there be?

Thanks,
Mark

As far as I know, changes to the data are not prohibited by whether or
not the data resides in a trusted folder. The trusted folder controls
whether or not VBA code can execute and which macro actions can execute.

So if the data is all in a back-end and all the code and macros are in a
front-end, then I would think that the front-end had to be in a trusted
location, but not so for the back-end.

If I am wrong, I wait correction.

'====================================================
John Spencer
Access MVP 2002-2005, 2007-2009
The Hilltop Institute
University of Maryland Baltimore County
'====================================================

I'm trying to unravel a problem at another site where a user with an Access
2007 frontend linked to the backend on a file server can only read records,

[quoted text clipped - 31 lines]

Thanks,
Mark