Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsFormsForms ProgrammingQueriesModules / DAO / VBAReports / PrintingMacrosDatabase DesignSecurityConversionImporting / LinkingSQL Server / ADPMultiuser / NetworkingReplicationSetup / ConfigurationDeveloper ToolkitsActiveX ControlsNew UsersGeneral 1General 2
Access DirectoryToolsTutorialsUser Groups
Related Topics
SQL ServerOther DB ProductsMS OfficeMore Topics ...

MS Access Forum / Multiuser / Networking / March 2006

Tip: Looking for answers? Try searching our database.

Interesting network/link problem

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Julia Boswell - 22 Feb 2006 13:26 GMT
All,

I have a company intranet which uses a 2003 Access db as a backend,
developed with Cold Fusion (purchased as an off-the-shelf intranet). It
works fine. However I want to query one of the tables in the back end and
run a report that users can access from a link. Here's my approach, which
hasn't worked so far....

I have created a new access db and linked it to the relevant table in the
intranet backend db. I have written an autoexec macro which runs some code
to open a form enabling the user to select the report in preview or print
mode, thus limiting the user's access to the tables etc.

The second access db is on a network directory that all users have edit
access to.

I then created a link from our intranet to the network directory using the
full file path name, in the hope that access will open with the form run by
the autoexec macro.

I have 2 problems with this:

1- some people cannot open the db from the intranet link, they get the
message "file already in use".
2 - those who can open the db from the intranet link, then get the message
"could not open ......mdb file already in use" - this is the intranet
backend db.

How on earth do I get around this? Please bear in mind that I'm not a cold
fusion developer, or ASP or anything similar. I can write rudimentary html
and am learning vb.net, but in early stages. I know we could distribute the
front end to all users but that's not an option we want to explore.

Any ideas appreciated.

Julia
Joan Wild - 23 Feb 2006 15:56 GMT
> The second access db is on a network directory that all users have
> edit access to.

Users need create and delete permission on the folder, in order to create
the associated ldb file.  Without the create permission, they will open the
database exclusively.

Signature

Joan Wild
Microsoft Access MVP

Julia Boswell - 27 Feb 2006 10:44 GMT
I've just double checked and everyone has full control so that isn't the
issue. Any other ideas?

Julia

>> The second access db is on a network directory that all users have
>> edit access to.
>
> Users need create and delete permission on the folder, in order to create
> the associated ldb file.  Without the create permission, they will open
> the database exclusively.
Joan Wild - 27 Feb 2006 14:55 GMT
You referred to 'intranet' as well as a 'network directory', which to me are
the same thing.

Do users have the full permission on both the folders involved?

Actually you should put a copy of the frontend on each users computer,
rather than on a shared folder.

Signature

Joan Wild
Microsoft Access MVP

> I've just double checked and everyone has full control so that isn't
> the issue. Any other ideas?
[quoted text clipped - 11 lines]
>> Joan Wild
>> Microsoft Access MVP
Julia Boswell - 28 Feb 2006 11:16 GMT
They have full permissions on the first directory, but not on the second and
we can't give them full permissions on that one. Unfortunately, we don't
want to put the front end on everyone's computer either.

Any other suggestions?

Julia
> You referred to 'intranet' as well as a 'network directory', which to me
> are the same thing.
[quoted text clipped - 19 lines]
>>> Joan Wild
>>> Microsoft Access MVP
Joan Wild - 28 Feb 2006 15:47 GMT
> They have full permissions on the first directory, but not on the
> second and we can't give them full permissions on that one.
> Unfortunately, we don't want to put the front end on everyone's
> computer either.
> Any other suggestions?

Not really.  Users need read/modify/create/delete permissions on the folder
that contains the mdb.  By sharing a frontend, you run the risk of
corruption.

Signature

Joan Wild
Microsoft Access MVP

Tony Toews - 01 Mar 2006 21:10 GMT
>Unfortunately, we don't
>want to put the front end on everyone's computer either.

Why not?  

An alternative is you could give each user a copy of the FE in a user
specific folder on the server.  Possibly in their home drive.

Tony
Signature

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

 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.