MS Access Multiuser - Connections not being released

Author

Connections not being released - becoming a pain

Pamela via AccessMonster.com

2005-09-29, 9:24 am

Hello.

I need to be able to occasionally get into a database to make updates,
however, when I ask the users to get out of the database, not everyone is
released (I have a function which shows all the connected users). Is there a
way to force Access to release all connections, or is there a way to prevent
connections top remain open once the user has closed out of the application?
This application is on a server & is shared by several users. The database
is not split. It is Access 2002. Any help would be appreciated. Thanks.

--
Message posted via webservertalk.com
http://www.webservertalk.com/Uwe/Fo...tiuser/200509/1

Jack MacDonald

2005-10-01, 11:23 am

Split the database. Every user should get their own copy of the FE on
their workstation. Only the tables belong in the shared BE. See
http://www.granite.ab.ca/access/splitapp/index.htm

On Thu, 29 Sep 2005 13:43:28 GMT, "Pamela via webservertalk.com"
<u11418@uwe> wrote:

>Hello.
>
>I need to be able to occasionally get into a database to make updates,
>however, when I ask the users to get out of the database, not everyone is
>released (I have a function which shows all the connected users). Is there a
>way to force Access to release all connections, or is there a way to prevent
>connections top remain open once the user has closed out of the application?
>This application is on a server & is shared by several users. The database
>is not split. It is Access 2002. Any help would be appreciated. Thanks.

********************
**
jackmacMACdonald@tel
usTELUS.net
remove uppercase letters for true email
http://www.geocities.com/jacksonmacd/ for info on MS Access security

Albert D.Kallal

2005-10-27, 8:31 am

>database
is not split.

You might want the network people to read the following article about
splitting:

http://www.members.shaw.ca/AlbertKallal//Wan/Wans.html

It is possible that the network people DO NOT understand the difference
between a file, and a application (on the other hand, I can't imagine people
managing computers and not being able to tell the difference between a file
and a application).

You, and you network people need to sit down and read the above article, as
it is important for them to understand the difference between files, and
that of software applications that run on a computer. Have them read the
above...

--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pleaseNOOSpamKallal@
msn.com
http://www.members.shaw.ca/AlbertKallal

Emma Hope

2005-10-27, 8:31 am

Hi Pamela,

I am not an expert like the wonderful guys who usually reply but i have also
had a similar problem which i sorted myself after getting similar 'split the
database' answers (which i cannot do).

I created a table called close in which i can add a value which is a time
and date. I then created a little form which has the current date and the
date from the 'close' form and then set a timer to refresh the values every
ten seconds, then if the current time passes the 'close' time the database
closes, using the "quit" command.

So points to note however, i had to do something that says after a minute
after the 'close' time, clear the cell on the form otherwise everytime you
reopen the database it closes because the time has passed.

You have to make sure that the form always opens for each user (i used
autoexec) and they cannot close it, i took away the [x] and won't let them
view the design.

It seems to work very well, even if there are 'ghost' users etc, i even
added to it so it works automatically at 7pm each night. I'll warn you it
took me a while to get everything refreshing correctly and i 'fudged'
somewhat as i couldn't get one bit to refresh, so i just applied a sort or a
filter on the one single record in the 'close' table which seemed to get it
to recognise/refresh the value.

Hope this helps.
Emma

"Pamela via webservertalk.com" wrote:

> Hello.
>
> I need to be able to occasionally get into a database to make updates,
> however, when I ask the users to get out of the database, not everyone is
> released (I have a function which shows all the connected users). Is there a
> way to force Access to release all connections, or is there a way to prevent
> connections top remain open once the user has closed out of the application?
> This application is on a server & is shared by several users. The database
> is not split. It is Access 2002. Any help would be appreciated. Thanks.
>
>
> --
> Message posted via webservertalk.com
> http://www.webservertalk.com/Uwe/Fo...tiuser/200509/1
>

Pamela via AccessMonster.com

2005-10-27, 8:32 am

Thanks for all the replies! I will definitely be splitting the database when
it is completely done (seems they constantly want something modified). I
have finally found the cause, right here in this great forum.

The cause was the use of conditional formatting in subforms. Removing the
conditional formatting in the subform fixed the problem of the "ghost
connections".

What was happening is: in the database that had the conditional formatting
in the subforms, if a user were to open it, then close it, the process would
still show as "running" in the Task Manager. This was my first clue &
allowed me to isolate the application causing the problem. If the process
was still running on the workstation, when they tried to open another mdb
file, (by double-clicking the mdb file) it would not open. Only way it would
open is if they were to open Access first, then open the file.

Anyway, it was this process that was still running which caused the "phantom"
connection & caused the ldb file to persist, even after the user closed out
of Access. Also explains why restarting the machine took care of the ldb
file/persistent connection.

Thanks! :-)

Emma Hope wrote:[color=darkred
]
>Hi Pamela,
>
>I am not an expert like the wonderful guys who usually reply but i have also
>had a similar problem which i sorted myself after getting similar 'split the
>database' answers (which i cannot do).
>
>I created a table called close in which i can add a value which is a time
>and date. I then created a little form which has the current date and the
>date from the 'close' form and then set a timer to refresh the values every
>ten seconds, then if the current time passes the 'close' time the database
>closes, using the "quit" command.
>
>So points to note however, i had to do something that says after a minute
>after the 'close' time, clear the cell on the form otherwise everytime you
>reopen the database it closes because the time has passed.
>
>You have to make sure that the form always opens for each user (i used
>autoexec) and they cannot close it, i took away the [x] and won't let them
>view the design.
>
>It seems to work very well, even if there are 'ghost' users etc, i even
>added to it so it works automatically at 7pm each night. I'll warn you it
>took me a while to get everything refreshing correctly and i 'fudged'
>somewhat as i couldn't get one bit to refresh, so i just applied a sort or a
>filter on the one single record in the 'close' table which seemed to get it
>to recognise/refresh the value.
>
>Hope this helps.
>Emma
>
>[quoted text clipped - 5 lines]

--
Message posted via webservertalk.com
http://www.webservertalk.com/Uwe/Fo...tiuser/200510/1

Sponsored Links