Making sure that correct version of client is used

[925069]

Hi guys,

I made a tool that is currently in use by the Marketing department of the company. It consists of a local client (Access 2003) and a source database (also Access 2003). Since some changes had to be implemented and a new version of the client was created, I would like to make sure that everyone is working with the new version. Is there a way to check this? I was thinking there should be something like 'OnConnect", but this does not seem to exist.

All help would be very much appreciated! Thx.

[PianoMan64]

Hi guys,

I made a tool that is currently in use by the Marketing department of the company. It consists of a local client (Access 2003) and a source database (also Access 2003). Since some changes had to be implemented and a new version of the client was created, I would like to make sure that everyone is working with the new version. Is there a way to check this? I was thinking there should be something like 'OnConnect", but this does not seem to exist.

All help would be very much appreciated! Thx.

The easy way to do this is to create a table in the client version of the MDB or MDE depending on which you're distributing, and have what version it is in it.
When you open to your first screen, you can have it check what version is the current version in the local table against a table on your backend that would also have the value of the current version. If the number is different, then they need to update there MDB or MDE file, by the process you've setup.

If you need more detail as to how to do this, please let me know, I'll be able to provide code examples on the areas that you don't know how to do?

Just ask, and I can answer.

Joe P.

[925069]

Thx, I also thought about this solution. Problem is that it was not implemented from the start. So the client is already distributed, with no version control. What I want to achieve is that I can do the check from the source db, preventing users from using the currnt version of the client and forcing them to install the new version.

[matthardwick]

I had this problem. I just changed the path of the database that they were already connecting to (or just the name of the file). Of course they then have an error, and you can say - oh you need the updated version - here install that and you should be OK.

Of course this updated version has a mechanism for for seeing what release they are using.