Accessing a database on a server

[TESA0_4]

Hi,
I have created an Access 2000 format database using Access2003 that has been
moved to a PC acting as a server for an 8 user local LAN. The database could
be accessed by all users on the network. The server and PCs use Win2000.
It was decided to apply greater security by creating a workgroup with
permissions. This was a first time experience for me - I used the Microsoft
'Step by Step Access 2003' publication to guide me.
The database and .mdw file were moved to the server from my laptop (WinXP)
and I created a shortcut on my laptop to access the db on the server.
I installed a shortcut on the PCs pointing to msaccess.exe on the PC and the
db and .mdw file on the server. Access opens but a message is displayed
'Microsoft Access cannot open this file. File located outside your intranet
or trusted site. Access will not open file due to potential security
problems.'
I have checked security in Internet Explorer and MS Access is enabled for
Intranet.
I also find that if I use a PC to create a .mdb file on the server the file
will be created but cannot then be subsequently opened from the PC.
It seems to me that creating a workgroup has created a security problem that
does not allow either a secured or unsecured database on the server to be
opened from any of the Win2000 PCs, whereas I can open databases on the
server using my WinXP laptop.
Can anyone offer some guidance? Thank you in anticipation.

 

[TESA0_4]

Hi,
From reading another thread I was led to the following link which solved my
problem:
http://support.microsoft.com/kb/303650
Hope this helps someone else.

 

[Tony Toews [MVP]]

I have created an Access 2000 format database using Access2003 that has been
moved to a PC acting as a server for an 8 user local LAN. The database could
be accessed by all users on the network.

You've already received a good answer to your specific problem.
However a future problem will be hitting you very shortly.

You want to split the MDB into a Front End MDB containing the queries,
forms, reports, macros and modules with just the tables and
relationships in the Back End MDB. The FE is copied to each network
users computer. The FE MDB is linked to the tables in the back end
MDB which resides on a server. You make updates to the FE MDB and
distribute them to the users, likely as an MDE.

See the "Splitting your app into a front end and back end Tips" page
at http://www.granite.ab.ca/access/splitapp/ for more info. See the
Auto FE Updater downloads page
http://www.granite.ab.ca/access/autofe.htm to make this relatively
painless.. The utility also supports Terminal Server/Citrix quite
nicely.

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/

 

[TESA0_4]

Tony and Joseph - Thanks very much for your advice. A work colleague with
significant Access experience and competence just dropped by and gasve the
same advice!!!

Regards,
Terry