Distributing Front End

[David Portwood]

I'm about to split my app into an FE and BE. I will copy my BE onto the
shared network drive along with the system.mdw file. No problem there. But
how do I get the FE's distributed to my users' local drives?

I suppose I could copy the FE temporarily to a shared network drive and then
run around to each user's computer to copy the FE onto the local drive. I'm
prepared to do this once, but I know I'll be making frequent changes to the
FE (possible the BE, too!) in the days to come. Seems like a lot of running
around.

I'm very much a newbie. Any suggestions or advice would be much appreciated.

 

[Ken Snell \(MVP\)]

Tony Toews (MVP) has a utility to copy updated versions of front end files
to users' computers:
http://www.granite.ab.ca/access/autofe.htm

 

[Peter Hibbs]

David.

You may also be interested in these -

http://www.rogersaccesslibrary.com/Otherdownload.asp?SampleName='BE_ReLink.mdb'

http://www.rogersaccesslibrary.com/Otherdownload.asp?SampleName='BE Update Utility.mdb'

Peter Hibbs.

 

[Larry Linson]

. . . But how do I get the FE's distributed
to my users' local drives?

I suppose I could copy the FE temporarily
to a shared network drive and then run around
to each user's computer to copy the FE onto
the local drive. I'm prepared to do this once,
but I know I'll be making frequent changes to
the FE (possible the BE, too!) in the days to
come. Seems like a lot of running around.

You _could_ do that if your users aren't capable of opening an Explorer
window and dragging-and-dropping a file. Mine always have been. For an
explanation of an approach that has worked nicely for me, see the article on
"versioning" at http://accdevel.tripod.com.

For users who can't or aren't supposed to drag-and-drop files, I've long
recommended MVP Tony Toews' AutoFEUpdater, which you can download from his
site, http://www.granite.ab.ca/accsmstr.htm.

Larry Linson
Microsoft Access MVP

 

[David Portwood]

I'll allow that most of my users can drag and drop a file. This is a relief.
I was overly concerned with the possibility of FE versions getting mixed
between users, but so what? If a user is too lazy to copy the latest version
of the fe he is welcome to continue using an earlier version.

 

[Paul Shapiro]

I find it simple to create a command file on a network drive that copies the
current front end to the user's computer, and then put a link on each user's
desktop to run that command file. Besides automatically distributing the
updates, it always refreshes the front end even when there haven't been
updates. Any corruption or bloat automatically disappears since that would
always be in the local copy. Speed has never been an issue- if a network is
good enough to support the back end, copying the front end file isn't a big
deal.
Paul Shapiro

 

[Tony Toews [MVP]]

I'll allow that most of my users can drag and drop a file. This is a relief.
I was overly concerned with the possibility of FE versions getting mixed
between users, but so what? If a user is too lazy to copy the latest version
of the fe he is welcome to continue using an earlier version.

Well, yeah, but.

1) Sometimes you need to make archetictural changes to your databases where the users
must have a few FE.

2) Sometimes there are bug fixes where you want to the user to be using the new FE.
Maybe not right this instance but definitely the next time they run the app.

Thus the free Auto FE Updater tool.

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
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

 

[Larry Linson]

I'll allow that most of my users can drag
and drop a file. This is a relief. I was overly
concerned with the possibility of FE versions
getting mixed between users, but so what?
If a user is too lazy to copy the latest version
of the fe he is welcome to continue using
an earlier version.

I am as certain as I can be without re-reading that article that I described
the two options: (1) new database available but optional, and (2) new
database mandatory.

The first option is for improvements or additional features that aren't
vital but the user may find helpful -- the user may not want to spend the
time to drag/drop (download) a copy until later;

The second option is for changes which, if not used, can cause problems or
damage to the database or which management has deemed that all users will
have, and the front end notifies the user and quits, if this is the case.

And, if that causes a problem, there's always the AutoFEUpdater. Some
clients prefer to start with AutoFEUpdater, and that's just fine with me.

Larry Linson
Microsoft Access MVP