Access error codes

L

Luke Bellamy

Hi - just wondering if their is an online database somewhere with the
Microsoft Access error codes. Access 2002 (XP)

I'm getting error:
31541 cannot open this file

and need more information.

Thanks,
Luke
 
L

Luke Bellamy

Yeah I googles that too but looking for a more detailed description
from Microsoft. Surely they should have one on the web.

I definately know it's a permission problem when the network server
was upgraded to windows 2003.
MDB File access locally is fine but not on the network drive.

Luke
 
D

Dodo

I definately know it's a permission problem when the network server
was upgraded to windows 2003.
Click to expand...

Then why wouldn't you make that network location "accessible" to that
particular user! ;-)))
One way or the other you have to turn the location into a trusted one
again.

I do not know your system setup but you can find plenty of info here:

http://search.microsoft.com/search/results.aspx?st=b&na=88&View=en-
us&qu=access+trusted+site

Or TinyURLed: http://heh.pl/&1wx

I use Access2000 myself but I understand version 2003 is more critical on
security issues.
 
L

Luke Bellamy

Thanks I'll check out the info. I'm addressing this problem remotely
(i.e going on what the IT people tell me) and they reakon the network
location is shared correctly with full permissions.
I don't have 2003 server so cannot test.

Thanks again,
Luke
 
A

Arvin Meyer [MVP]

You need to have Modify (Read, Write, Create, Delete) permissions for that
user on that folder in the network drive in order to be functional for
Access. Anything less will generally cause problems. All users need those
permissions. If you want finer granularity in your database security, it is
better to use user-level security within Access.
--
Arvin Meyer, MCP, MVP
Microsoft Access
Free Access downloads:
http://www.datastrat.com
http://www.mvps.org/access

Luke Bellamy said:
Yeah I googles that too but looking for a more detailed description
from Microsoft. Surely they should have one on the web.

I definately know it's a permission problem when the network server
was upgraded to windows 2003.
MDB File access locally is fine but not on the network drive.

Luke
Click to expand...
 
D

Dodo

You need to have Modify (Read, Write, Create, Delete) permissions for
that user on that folder in the network drive in order to be
functional for Access.
Click to expand...

I understood it to be an Access security problem as the error code came
from Access itself.

Or is Access looking at server permissions as well?
 
L

Luke Bellamy

Yep I also understand that. It was all working fine until they upgraded to
Windows server 2003 and I got them to confirm they can create, modify,
and delete an empty text file in that location. So they do have full access
through explorer.

Luke

Arvin Meyer said:
You need to have Modify (Read, Write, Create, Delete) permissions for that
user on that folder in the network drive in order to be functional for
Access. Anything less will generally cause problems. All users need those
permissions. If you want finer granularity in your database security, it is
better to use user-level security within Access.
--
Arvin Meyer, MCP, MVP
Microsoft Access
Free Access downloads:
http://www.datastrat.com
http://www.mvps.org/access
Click to expand...
 
L

Luke Bellamy

OK so I've just been playing around with windows 2003 server.
When you setup a share and set the permissions in the same tab
as sharing it only seems to apply to directory browsing using apps
such as explorer.
So I could map and play with files through explorer but not my app
that uses link tables.
In the security tab beside the sharing tab I played with the permissions
and this allows apps such as mine to access that directory area and
read/write
to the database.

Pretty simple really but when your giving support remotely it's hard to
understand
what security they have set and what they mean by "full permissions".

Luke
 
D

Dodo

Yep I also understand that. It was all working fine until they
upgraded to Windows server 2003 and I got them to confirm they can
create, modify, and delete an empty text file in that location. So
they do have full access through explorer.
Click to expand...

Wasn't it Access that reported that the file resided in an untrusted
domain?

I do not know Access security and I do not know server 2003.

I presume that the "old" security settings in Access conflict with the
"new" domain (name) constituted by the new server (software).

So, probably the security settings in Access have to be changed to the new
situation/domain(name).

At least, that is what I can think together from "old" experience with a
Novell 3.12 server network environment and local security for workstations
running applications different from Access.
 
L

Luke Bellamy

Yes access 2002 reported the error. I don't have any security in the Access
application
except it's an mde front end.
What security settings are you referring to?

As I said, it worked fine with Windows 2000 server but not Windows 2003
server.

Luke
 
D

Dodo

I don't have any security in the Access application
except it's an mde front end.
What security settings are you referring to?
Click to expand...

As I said, I do not know the specifics of Access and server 2003 security,
nor have I worked with split databases.

I found that it might have to do with IE or an upgrade to XP SP2!?

These may be of further help:

http://support.microsoft.com/default.aspx?scid=kb;en-us;Q303650

http://www.ahinc.com/support/access.htm

http://www.dbforums.com/t1082792.html

http://forums.aspfree.com/archive/t-42399/problem-with-security-server

http://archives.postgresql.org/pgsql-odbc/2004-10/msg00110.php

These and more googles found here:

http://www.google.nl/search?
q=located+outside+your+intranet+or+on+an+untrusted+site&sourceid=mozilla-
search&start=0&start=0&ie=utf-8&oe=utf-8&client=firefox-
a&rls=org.mozilla:en-US:eek:fficial

It must have to do with a possible change in domain (name) when going from
the old to the new server (software) version and (security) settings for
approaching files within that domain. Access now sees it as outside your
LAN/intranet or sitting in an untrusted zone/site.
 
L

Luke Bellamy

All sorted by adjusting the IE security settings adding the server
to the trusted zones.

Thanks for your help Dodo... much appreciated
 
D

Dodo

All sorted by adjusting the IE security settings adding the server
to the trusted zones.

Thanks for your help Dodo... much appreciated
Click to expand...

It was a pleasure!

Who could have thought out by logic that it is IE determining the
accessibility of files on a server?!
 
Top