Update Access Application

[trueness]

Hello,

Im new in forum, I searched but I coulndt find topic regarding to my issue, and if it exist, so sorry,

I have a access database in my server, and users connect to database via Ms Access application, Sometimes I modified the application, ( add form, add report, change something, a new table connection or something else.. ) but this time, I have to send this application to all user, And users delete old one and use the new,

I want to add a button for update and when user clicked this button, Access application update itself from server ( the path that I load new application ) or delete itself and load the new one from server,

Thanks,

 

[trueness]

Hello to everybody,

Any reply ?

 

[melissa_may1]

Hi Trueness,

I have an idea.

Why not put the application in a shared directory on the server, then point each workstation to the application there?

This way, when you need to change the application, all you have to do is update it on the server.

One possible problem with this scenario, however, is if you change the application while someone is running it. In that case, you would need to be sure that all of the users exit the application before you update it.

Hope this helps!

 

[spikepl]

Err... melissa... that is not the way! It bogs down the network, and the users will share the front end, a nono!

You need to do a bit more searching, look for frontend updates (or updater) there is some code floating around this site and links to tools (free and commercial) elsewhere.

 

[speakers_86]

You can use Bob Larson's tool from here.

 

[MSAccessRookie]

Hi Trueness,

I have an idea.

Why not put the application in a shared directory on the server, then point each workstation to the application there?

This way, when you need to change the application, all you have to do is update it on the server.

One possible problem with this scenario, however, is if you change the application while someone is running it. In that case, you would need to be sure that all of the users exit the application before you update it.

Hope this helps!

This would (in effect), create a group of users that shared a single Front End, which goes against the reason for splitting out the Front End in the first place. Add that to the Network issues that spikepl discribes, and you get plenty of reason to find another way. An Application updater like the one that speakers is referring to is probably your best bet in this situation.

-- Rookie

 

[melissa_may1]

Hi All,

You are all correct!

I was thinking that the network traffic wouldn't be a big deal, since it was only the application front-end that was moving, but that's a valid concern.

I was also thinking about some code that would compare the application date on the server with the one on the workstation, and update if necessary.

Having thought about this more, that wouldn't work well in a situation where the updated front end made changes to the table structure, or to any logic that conflicts with a previous version.

Ideally all of the workstations would be updated together, so nobody is running a prior version at any time.

So, good that you all stepped in to give the correct answer.

I'll just slink away quietly...

 

[MSAccessRookie]

Hi All,

You are all correct!

I was thinking that the network traffic wouldn't be a big deal, since it was only the application front-end that was moving, but that's a valid concern.

I was also thinking about some code that would compare the application date on the server with the one on the workstation, and update if necessary.

Having thought about this more, that wouldn't work well in a situation where the updated front end made changes to the table structure, or to any logic that conflicts with a previous version.

Ideally all of the workstations would be updated together, so nobody is running a prior version at any time.

So, good that you all stepped in to give the correct answer.

I'll just slink away quietly...

There is no need to slink, Melissa. Like my tag line says, "No one is expected to know everything and we can all learn from each other if we try.". I still learn new things here all of the time.

 

[melissa_may1]

Hi MSAR,

Thanks for the kind words.

I suppose I won't slink, then.

Just sulk...

Seriously, I'm glad that you all corrected my post, and I did learn more by having participated in the discussion.

Some members in other forums are quick to tear apart someone who offers bad advice, regardless of the poster's intent.

I'm happy to see that you all caught my error, but were kind in your presentation.

Though I'm a bit rusty in Access, I have been programming for years, and (usually) have a good perspective on things.

Thanks again for your reply!

 

[spikepl]

If you miss a chainsaw massacre we can provide that too

 

[melissa_may1]

Ummm... I'm thinking I'll wait on that, but thank you for asking!

I've got enough trouble on my "Can't find a way to trap an error" thread!

I think that I'll self-implode before that's finished and working...

:|