Group:  Microsoft Access ยป microsoft.public.access.multiuser
Thread: Interesting network/link problem

DotNetBag
.NET Development Newsgroups

HTVi
TV Discussion Newsgroups

Our Hot Pick: Rising Antivirus 2006 - Certified by TUV & Checkmark! Get 10% discount by entering this coupon code: ONDISCOUNT10
Rising Antivirus 2006

Interesting network/link problem
"Julia Boswell" <jcrackne[ at ]hotmail.com> 22.02.2006 13:26:19
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


Re: Interesting network/link problem
"Joan Wild" <jwild[ at ]nospamtyenet.com> 23.02.2006 15:56:18
Julia Boswell wrote:
[Quoted Text]
>
> 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
Microsoft Access MVP


Re: Interesting network/link problem
"Julia Boswell" <jcrackne[ at ]hotmail.com> 27.02.2006 10:44:40
I've just double checked and everyone has full control so that isn't the
issue. Any other ideas?

Julia
"Joan Wild" <jwild[ at ]nospamtyenet.com> wrote in message
news:eu$rvGJOGHA.420[ at ]tk2msftngp13.phx.gbl...
[Quoted Text]
> Julia Boswell wrote:
>>
>> 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
> Microsoft Access MVP
>


Re: Interesting network/link problem
"Joan Wild" <jwild[ at ]nospamtyenet.com> 27.02.2006 14:55:11
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.


--
Joan Wild
Microsoft Access MVP

Julia Boswell wrote:
[Quoted Text]
> I've just double checked and everyone has full control so that isn't
> the issue. Any other ideas?
>
> Julia
> "Joan Wild" <jwild[ at ]nospamtyenet.com> wrote in message
> news:eu$rvGJOGHA.420[ at ]tk2msftngp13.phx.gbl...
>> Julia Boswell wrote:
>>>
>>> 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
>> Microsoft Access MVP


Re: Interesting network/link problem
"Julia Boswell" <jcrackne[ at ]hotmail.com> 28.02.2006 11:16:39
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
"Joan Wild" <jwild[ at ]nospamtyenet.com> wrote in message
news:uxaHP36OGHA.2624[ at ]TK2MSFTNGP12.phx.gbl...
[Quoted Text]
> 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.
>
>
> --
> Joan Wild
> Microsoft Access MVP
>
> Julia Boswell wrote:
>> I've just double checked and everyone has full control so that isn't
>> the issue. Any other ideas?
>>
>> Julia
>> "Joan Wild" <jwild[ at ]nospamtyenet.com> wrote in message
>> news:eu$rvGJOGHA.420[ at ]tk2msftngp13.phx.gbl...
>>> Julia Boswell wrote:
>>>>
>>>> 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
>>> Microsoft Access MVP
>
>


Re: Interesting network/link problem
"Joan Wild" <jwild[ at ]nospamtyenet.com> 28.02.2006 15:47:53
Julia Boswell wrote:
[Quoted Text]
> 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.

--
Joan Wild
Microsoft Access MVP


Re: Interesting network/link problem
Tony Toews <ttoews[ at ]telusplanet.net> 01.03.2006 21:10:51
"Julia Boswell" <jcrackne[ at ]hotmail.com> wrote:

[Quoted Text]
>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
--
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

Home | Search | Terms | Imprint | Contact
Newsgroups Reader - provided by WiredBox.Net