Locking...

[u7djo@hotmail.com]

All,
I've had to develop a series of VBA scripts to interact with an AS400
system and have these held collectively in an Access database. The
input data is managed using automation and Excel without writing to the
database itself. The database does however, have some lookup tables
that are used as well as forms for navigation and as a front end to
each script.
My problem is that the application has multiple users (>150) and that
they're not always very good at remembering to log off, close things
down etc. and as such I occasionally get the LDB file locked by users
who are no longer connected.
I'm considering splitting the database FE/BE and having a word with our
infrastructure team to see if they can update the FE on each user's
machine as and when updates occur but this would be a bit of a pain to
manage. Does anyone have any suggestions about how else I could manage
this?

Thanks in advance

Dave

[Wayne Phillips]

Re: Locking...

Splitting your database into FE/BE is generally a good idea anyway to
improve performance over networks particularly when many users are
connecting at once.

Have a look at this Auto FE Updater by Tony Toews....

http://www.granite.ab.ca/access/autofe.htm

Regards,

Wayne Phillips
http://www.everythingaccess.com - Access Database Repair Service

<u7djo@hotmail. com> wrote in message
news:1114678765 .315241.170160@ o13g2000cwo.goo glegroups.com.. .[color=blue]
> All,
> I've had to develop a series of VBA scripts to interact with an AS400
> system and have these held collectively in an Access database. The
> input data is managed using automation and Excel without writing to the
> database itself. The database does however, have some lookup tables
> that are used as well as forms for navigation and as a front end to
> each script.
> My problem is that the application has multiple users (>150) and that
> they're not always very good at remembering to log off, close things
> down etc. and as such I occasionally get the LDB file locked by users
> who are no longer connected.
> I'm considering splitting the database FE/BE and having a word with our
> infrastructure team to see if they can update the FE on each user's
> machine as and when updates occur but this would be a bit of a pain to
> manage. Does anyone have any suggestions about how else I could manage
> this?
>
> Thanks in advance
>
> Dave
>[/color]