Making Sure Client is Up-to-Date

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hello,

What is the best way to make sure that the local user client is up to date?
I have a split db where the client is on the local users pc and the BE DB is
out on the server. Currently I have a check upon opening the client that
verifies that the client version matches the master client version stored in
the BE. If the versions don't match it displays a message that informs the
user that their client is out of date. My problem is that users are not
updating their client, which is causing problems. My question is...is there
a way to automatically update the client if the versions do not match? Maybe
the transferdatabase function?

thanks in advance.
 
Thanks Doug. I have been playing with the FE Updater created by Tony Toews
and maybe I am missing it but it looks like the user still needs to perform
an action to execute the update. Is this true? What methods have you used to
start to the update on the client workstation. Sorry..but feeling a little
confused.
 
I haven't used the utility myself, but I believe you give the user a
short-cut pointing to the utility. The user double-clicks on that shortcut,
which checks that the user has the most recent version, downloads the most
recent version if not, and then launches the application for the user.
 
Doug many thanks again. Yes. you place the command line that the FE updater
produces within a shortcut and it copies over the newest and greatest version
if a version mismatch. THANKS AGAIN FOR EVERYTHING.
 
Probably a bit late for solutions now but...

My users have a batch file and get the latest copy of the FE every time
(due to contstant updates).

This is it:

-------------------
@echo off

if not exist "h:\ClientFolder" mkdir "h:\ClientFolder"
xcopy /y /q "G:\Dev\Database\Data\FrontEnd\Latest Version\*.*"
"h:\ClientFolder\*.*"
start /max D:\Apps\Micros~1\Office\msaccess.exe
"h:\ClientFolder\FEClient.mde"
exit
-------------------
 
Back
Top