Updating a Database from an Online Repository

[burt1215]

Hello,



I have a database that is in its early stages.

As of right now I've put out ten updates.
I do all the building on my laptop, but the database runs on the servers at my work.
Right now, my procedure for updating is to go into work with my flashdrive and move the file over.

I would like a way to be able to upload versions onto a repository somewhere, and to have the database read the repository, and prompt the user to update.
If the user accepts, the database will download and update to the new version.

This doesn't have to be automatic. I would be fine sending out an email letting people know a new version is out and having a "Check for Updates" button that the user clicks.

I would also like a way to roll back to a previous version.

I have the database split up, so really, I just want the front end updating.
But I want everything on the front end updating: forms, modules, queries, reports.

I did some research online, and this might be called source control, but I'm not sure, as articles I read on source control were confusing...

Anyway, if someone could help me out, that would be great.

[ranman256]

By 'updates' , do you mean:
update the FE code?
or
update the BE data?

if FE, you make the updates to the code and email it to all users.
if BE, you must keep the single db on a server so all users can access it. If you are updating the data on the laptop from out in the field. Then once you return to the main server, you must copy the BE back to the server.
If you are updating both local laptop and server data simultaneously , then thats more difficult.

[burt1215]

As I said in my original post, I want everything on the front end updating: forms, modules, queries, reports.

Here are some examples of some updates.
-I edited the VBA in a module, fixing a bug.
-I changed the Sequel Definition of a query, now it pulls different, or better information.
-I changed the "Can grow" property of some labels on my report, fixing the formatting when text gets too long.
-I added an entirely new form.

When I make a new version, I'll do any number of the above examples (not limited to, cause I definitely do a lot more from time to time).
So from version x.x1 to x.x2 we can have 10 or so different things change between forms, reports, queries, and modules.

On occasion I'll put out an update to the BE.

For example
-I'll add a new field in a table
-I'll add a completely new table

However, I'm not really focusing on the BE with this post.

So you have an app on your phone. Let's say Google Chrome.
One day, your phone gives you a notification.
"Google Chrome Needs to Be Updated: Click Here to Update"
So you click and your phone updates Google Chrome from version x.x1 to x.x2.

That's what I'm trying to do with the FE.
I want to put version x.x2 somewhere online; somewhere in the cloud.
Then I want to send an email out to the clients.
"Version x.x2 is out and available for download."
The clients then open up x.x1, click a button labeled "Check for Updates"
A prompt comes up "A New Update Was Found: x.x2. Would You Like To Download?"
The client clicks "Yes."
x.x2 is downloaded and a prompt comes up "Please restart the database to apply changes."
The database is closed and reopened, and now we're running x.x2.

Behind the scenes, the database is going to:
-Check for a new version
-Download the new version
-Replace the old version with the new version

That's about as clear as I can make it.

[orange]

An alternative, but similar approach, often discussed in forums goes something like this.

The latest accepted current front end is stored in a known shared location.
You have code in your front end that checks for the latest accepted version. If the current FE does not match the latest current version, the latest current version is downloaded to your PC and you are automatically using the latest accepted version.

When development/developer has modified and tested the front end, it is moved to the known shared location on the server and replaces the previous front end. When any user logs on, a check is automatically made to compare his/her Front end with the latest accepted front end.

You can google for specific implementations/ variations.

[burt1215]

Yeah. That's pretty much what I'm looking for.

I don't want to force a user to use the most current FE version. Like, I want to give them the option to update, but if they don't it's not my problem.

But taking what you've said, I can do some editing to make it look how I want.

Does this method have a name?