New front end required all users to exit backend

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Zenon - 23 Feb 2006 17:01 GMT

I have a split application where 12 or so users have a copy of the
front end on their machines, all linked to the same back end. When a
new version of the front end is distributed to each user, because of
requirements changes or upgrades, it appears that I cannot link the
newly installed front end to the back end as long as anyone else is in
it (and there is a locking file in existence). Is this true? If so,
this means that 12 people have to exit the application while I install
the new client on each machine and then link it to the back end. Is
there a better way so that 11 could keep working while I update them
one at a time?

thanks

Reply to this Message

George Nicholson - 23 Feb 2006 18:02 GMT

>... it appears that I cannot link the
> newly installed front end to the back end as long as anyone else is in
> it (and there is a locking file in existence). Is this true?

No, it shouldn't be an issue. Only if someone had the backend open
exclusively should there be an issue, but if you have more than one person
in it already, that's a non-starter.

> Is
> there a better way so that 11 could keep working while I update them
> one at a time?

Check out Tony Toew's invaluable freeware:
http://www.granite.ab.ca/access/autofe.htm

This requires that a copy of "current" version of the FE be on the network.
Once implemented properly, when each user uses their shortcut for your app,
Tony's app acts as a middleman and checks the user's local version of the FE
against the Network's, and copies the "new" version to the user's local
drive when appropriate. As long as the "new" FE is already pointing to the
proper backend with UNC syntax or common drive mapping, reconnecting
shouldn't be an issue.

If reconnecting remains an issue for some reason, you might want to check
out the following, which you might be able to adapt to automate the relink
process, depending on your setup:
http://www.mvps.org/access/tables/tbl0009.htm

HTH,

Signature

George Nicholson

Remove 'Junk' from return address.

>I have a split application where 12 or so users have a copy of the
> front end on their machines, all linked to the same back end. When a
[quoted text clipped - 8 lines]
>
> thanks

Reply to this Message

Zenon - 23 Feb 2006 20:59 GMT

Thanks very much

Perhaps my ADD kicked in and I didn't give the linked table manager
enough time. The status bar seemed not to move, and after about a
minute I gave up.

Reply to this Message

George Nicholson - 24 Feb 2006 19:15 GMT

ah, the status bar...

FWIW, my theory is that table-related status bars are scaled on the number
of tables, not their combined size. This means that if you have one table
that is very, very, very large and 9 small tables, the status bar can
appear to hang at 10% for minutes and then rush to completion in the blink
of an eye. (or zip to 90% and then appear to hang...). Patience usually
pays off. Go get another cup of coffee. :-)

HTH,

Signature

George Nicholson

Remove 'Junk' from return address.

> Thanks very much
>
> Perhaps my ADD kicked in and I didn't give the linked table manager
> enough time. The status bar seemed not to move, and after about a
> minute I gave up.

Reply to this Message

Tony Toews - 24 Feb 2006 21:41 GMT

>Thanks very much
>
>Perhaps my ADD kicked in and I didn't give the linked table manager
>enough time. The status bar seemed not to move, and after about a
>minute I gave up.

Ah, yes, it isn't the best. Try using the code at Relink Access
tables from code
http://www.mvps.org/access/tables/tbl0009.htm

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

Reply to this Message