Front End Update Issues

  • Thread starter Thread starter Brig
  • Start date Start date
B

Brig

I split our database into two different parts, FrontEnd and BackEnd.

What I did is copied the FrontEnd to each users that are currently using the
database.

Since we only have 5 users using the database, its been easy to update the
FrontEnds by walking to the desktop and copying on their desktop the updated
FrontEnds.

I would like to automate this update to their front ends by using the
briefcase.

1. I would like to create a MasterFront end that is located in a shared
folder in the server.
2. At each workstation, I would like to create a briefcase and put a copy
of the FrontEnd in there.
3. Only 1 person is doing modifications on the FrontEnd
4. After each modification, we will instruct the user to update their
briefcase and get the most updated version.

Let me know if the above steps will work.

I am more than happy to hear if you have a better solution or
recommendation.

Thank you.
 
Brig,

I do this all the time--update the client applications without visiting the
users' workstations. Create a table in the back-end called
'tblCurrentVersion' with a field, call it 'VersionNumber' and make it a
number, a double. Here's an example:

1.2

In the front-end, create another table--call it 'tblLocalVersion' with a
field, call it 'LocalNumber' and make it a number too, a double again.
Here's an example:

1.2 (The two version numbers should match)

Link the back-end's tblCurrentVersion into the computer's application (UNC
or drive-mapping). Then create an event procedure on a splashscreen (such as
using the OnLoad event) to perform a comparison between the two version
numbers, if they are not equal, 'call 'a batch script within the event
procedure--use the batch script to remove the existing application from the
user's computer, then install the new application (install if from the
network share to the computer's local application folder).

So how does it work? If you update the computer application, place the
updated version (with the next version number) in the network share. Then
change the back-end's version number.

The next time a user opens the application on their desktop, the program
will perform the comparison; the program's OnLoad event will 'fire' the
update because the version numbers no longer match. Thus, the batch script
will uninstall (delete) the old version on the user's computer. Then the
batch file will install the new version (with the matching version number)
on the user's computer; therefore, replacing the application.

Note: You can make the whole process transparent for the users whereas you
can even launch the updated application via the batch file.

Basically, when the user click the desktop icon, the whole process can take
place without any user intervention at all. If you would like some more
details, I can give you more details: example source code, batch scripts,
etc. That is, unless somebody has a brighter idea out there.

Best regards,

Todd Shillam
 
Thank you very much for the prompt response.

I will both investigate Joan and Todds options and see which works best.

For the mean time, I will continually walk to each of the user's workstation
and update the frontends like the old fashion way.

Thanks again.
 
Back
Top