Need an Auto FE Updater

[David Portwood]

I am in desperate need of an Auto FE Updater. I recently deployed an app to
more than thirty users and now I'm running around like a jackrabbit trying
to get the latest updates to everyone.

I looked at Tony Toews' product but it seemed a bit complicated. I don't
know anything about .ini files or .cmd files, for instance.

What I do now is copy my local FE file to a shared folder on the network
then go around to each workstation and copy and paste it into the user's "My
Documents" folder. The user launches from a shortcut on his desktop. And
yes, it would be great if my users could do this for themselves, but many of
them can't, many of them won't be bothered, and more than a few are just
jerks who enjoy watching me run around.

Help! Please! Is there a simple way that a dummy like me can automate this
process? Assume I don't know anything about creating .ini files or .cmd
files, etc.

 

[Tony Toews [MVP]]

I am in desperate need of an Auto FE Updater. I recently deployed an app to
more than thirty users and now I'm running around like a jackrabbit trying
to get the latest updates to everyone.

I looked at Tony Toews' product but it seemed a bit complicated. I don't
know anything about .ini files or .cmd files, for instance.

You can take the sample INI files supplied with the Auto FE Updater
and customize them to meet your requirements. To edit them just
double click on file in Windows Explorer and Notepad should open it
up.

Ignore the .cmd files for now as you will likely not need them.

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/

 

[David Portwood]

I looked again at your product as described on your website and now it
really looks complicated. Reminds me of the "for ages 12 and up" kits I used
to buy for my kids, most of which are still in the garage. I'm sure your
product is wonderful if only I knew how to install it and use it, but I
think I'd be days or even weeks fumbling around with it and my boss doesn't
have that kind of patience.

What I'm looking for is a simple product with a simple "step 1: do this,
step 2: do that" set of instructions. Plug and play. Sorry to admit, I don't
have the knowledge and/or smarts to make use of much else.

I certainly don't want any instructions with the phrase "server share" in
them. I have only a vague idea what a server is and I don't care who or what
it shares with. How did I develop a multiuser Access application in the
first place? Probably some sort of Divine intervention was involved.

If anybody knows of a simple product such as I've described please respond.
I can't believe I'm the only one having difficulties here although I can
easily believe I'm the only one owning up to it in a public forum.

 

[Scott McDaniel]

I looked again at your product as described on your website and now it
really looks complicated. Reminds me of the "for ages 12 and up" kits I used
to buy for my kids, most of which are still in the garage. I'm sure your
product is wonderful if only I knew how to install it and use it, but I
think I'd be days or even weeks fumbling around with it and my boss doesn't
have that kind of patience.

What I'm looking for is a simple product with a simple "step 1: do this,
step 2: do that" set of instructions. Plug and play. Sorry to admit, I don't
have the knowledge and/or smarts to make use of much else.

I certainly don't want any instructions with the phrase "server share" in
them. I have only a vague idea what a server is and I don't care who or what
it shares with. How did I develop a multiuser Access application in the
first place? Probably some sort of Divine intervention was involved.

There's always this:

http://www.fmsinc.com/Products/startup/index.asp

Pricey, but may be a bit simpler to implement.

Many people do it with a simple batch file, but often that's not robust enough. I built my own updater which works a lot
like Tony's, but it requires just as many steps to implement, and isn't for the faint of heart.

And - if you're not sure what a server share is, you might want to solicit some experienced assistance in dealing with
your database and deployment. Local usergroups are good resources, or perhaps there's someone else in your organization
that is more experienced with directories, permissions, etc etc

If anybody knows of a simple product such as I've described please respond.
I can't believe I'm the only one having difficulties here although I can
easily believe I'm the only one owning up to it in a public forum.

Scott McDaniel
scott@takemeout_infotrakker.com
www.infotrakker.com

 

[Peter Hibbs]

David,

Some time ago I write a simple program in Access 2000 to update the
front-end file (or any other type of file for that matter) on a number
of PCs on a network. Basically you just install the program on the
server PC (the one with the back-end file) and then set it up with the
built-in wizard to copy a database file to all the selected PCs on the
network. Once it has been set up the user just clicks a button and the
copying is done automatically. If you would like a copy please email
me at (e-mail address removed) (leave off the NOSPAM bit).

Having said all that I still think that Tony's updater is better as
the problem with mine (if you can call it a problem) is that you have
to make sure all the target PCs are switched on and not using the
database file that you are trying to update first. But if you want to
try it out you are welcome to a copy.

HTH

Peter Hibbs.

 

[David Portwood]

There's always this:

http://www.fmsinc.com/Products/startup/index.asp

Pricey, but may be a bit simpler to implement.

Many people do it with a simple batch file, but often that's not robust
enough. I built my own updater which works a lot
like Tony's, but it requires just as many steps to implement, and isn't
for the faint of heart.

And - if you're not sure what a server share is, you might want to solicit
some experienced assistance in dealing with
your database and deployment. Local usergroups are good resources, or
perhaps there's someone else in your organization
that is more experienced with directories, permissions, etc etc

Remarkably, I've been able to complete and successfully deploy a multi-user
Access application which has been quite well received even without knowing
what "server share" means. But thank you for your advice.

By the way, if you built something that is "not for the faint of heart" you
have a product that you probably should be embarrassed to mention. A good
product is exactly for the faint of heart.

 

[David Portwood]

I could not guarantee that all my users' computers are turned on and/or that
they are not currently using the system when I tried to update the file.
However, it sounds like what you have is close.

What happens if the user's computer is not turned on or if he is currently
using the file I'm trying to download? Does your program blow up, or does it
print an error message and continue? Does it keep a list of successful
downloads? If it did that much, I think I would be interested.

 

[Peter Hibbs]

David,

Yes, it's not that flaky. If the file cannot be updated for any reason
it shows an error message and carries on to the next one. It also
keeps a record of all updates and errors which can be printed out. If
the new version of your database causes any problems you can roll back
everyone's copy to the previous version as it keeps a back up copy of
that each time you run the program. You can also select which PCs you
want to update so that any that were switched off during the original
update can be updated at a later date.

Peter.

 

[Guest]

David:

O.K., I'm owning up to my ignorance in regards to this INI file issue. It
just won't gel. I plan on requesting Peter Hibbs' program and wanted to know
if you have used it and if so, what your experience has been. Thanks!

Nicole