I have an Access 2003 database that is used by around sixty users.
Routinely I can't gain access, even late at night after I KNOW that no
one is using it. The database is stored on a server that is accessed
through a Citrix environment. I've implemented an inactivity timer
that still doesn't seem to get the job done.
Any ideas?
"shayvillere@gmail.com"
news:5eb81cdc-b44c-4601-afe3-a9ada2b9e75f@v67g2000hse.google groups.com...
> I have an Access 2003 database that is used by around sixty users.
> Routinely I can't gain access, even late at night after I KNOW that no
> one is using it. The database is stored on a server that is accessed
> through a Citrix environment. I've implemented an inactivity timer
> that still doesn't seem to get the job done.
>
> Any ideas?
In a Citrix environment, if a user disconnects without logging out the
application continues to run. That's one of the reason you can use an Access
application over WAN with Citrix. The application may be open when no users
are connected. If your serve is set to end the session, it may not delete
the lock file.
On Fri, 25 Jan 2008 12:47:31 -0800 (PST), "shayvillere@gmail.com"
MSFT has an LDB viewer that can give you insights into who still has
the app open (according to Access).
Also, Windows can give you some info: My Computer > Manage > Shared
Folders > Open Files.
Inactivity timers are nice, but not foolproof. For example they won't
close the app when a MsgBox is showing.
-Tom.
>I have an Access 2003 database that is used by around sixty users.
>Routinely I can't gain access, even late at night after I KNOW that no
>one is using it. The database is stored on a server that is accessed
>through a Citrix environment. I've implemented an inactivity timer
>that still doesn't seem to get the job done.
>
>Any ideas?
On Jan 25, 3:47=A0pm, "shayvill...@gmail.com"
wrote:
> I have an Access 2003 database that is used by around sixty users.
> Routinely I can't gain access, even late at night after I KNOW that no
> one is using it. =A0The database is stored on a server that is accessed
> through a Citrix environment. =A0I've implemented an inactivity timer
> that still doesn't seem to get the job done.
>
> Any ideas?
I had this problem a few years back. If you're an admin, you have
recourse. If you're an end user, your voice won't be heard.
What I did was write a small script to log users onto the
application. When a user logs on, I write their name and time logged
on into a table. When they exit the application, I write their time
they logged off. If users logged on and didn't log off before leaving
for the night, I reported it to my manager, who would then verbally
abuse and threaten with a written warning anyone whom I reported. If
they were logged in when I needed access at night, I reported the
same. After a week or so of this, I was home free.
I originally used a boot function to kick everyone off, but Citrix
prevented it from being useful.
The biggest problem is users who don't close their applications at
night since they know they're running on a server that will stay on.
Make your manager beat it into people that connections MUST be closed
and you won't have the problem.