Linking a Database

[Eddie Mason]

Hi All,

Can anyone help with the following problem?

I have a database, which consists of a Data.mdb and a front-end.mdb that I regularly update. The problem is when work is done by a third party on the end users computers either the data or the end-user part of the database gets changed. If it’s the data then the users believe that information has been lost, and if it’s the front-end the users get confused because it does not work as it should. Is there any way of linking the front end to the back end for a specific version? So that it tells them that either the incorrect back end has been linked or that the front-end version is incorrect.

Regards

Eddie

 

[chenn]

If you are using a front end on the user's pc, and a back end on a server (for all users to access) then you shouldn't have a problem with pc changes. Just make sure that the user always has the most recent version. In a client - server environment this shouldn't be an issue.

If you really want the "version control" then you could add a table with the correct version into the front end (local table) and to the back end. This way when you open the database you could check to make sure that this is the correct version.

 

[Eddie Mason]

Hi Chenn,

Thanks for the advice, is it possible to stop the application from opening if the front end number is not the same as the the back end number?

Regards

Eddie

 

[dcx693]

Eddie Mason, I believe chenn already answered your question in his last paragraph.

Are you unsure about the actual mechanics of it? You can get at the version number stored in the table by using a dlookup, running a query, or opening the table as a recordset using DAO or ADO.

 

[chenn]

You cannot make the database not open, but you can make it close right after it does. The easiest way is probably to use a recordset that queries the local table and the linked (to backend) table to return the versions. Keep in mind that these versions are manual updates to tables on your part. If the versions don't match, close the database. This will make it appear as if the database tries to open but failes. You could even add a message box indicating the version problem. Put this code either in the autoexec macro, or on the load event of the main form.

Honestly, I wouldn't bother with this. I know you posted for a reason, but you are only adding to your over-head and the amount of work you need to do. The last thing you need to do is screw up the data version on the server and lockout all your users. Easy to fix, but a pain for you and the users.

I don't know your situation, but I recommend that you follow a release schedule. Make changes to you database when needed, test and release the version to the users. This way all users are always using the same program and you don't have to worry about versions. If need be, keep backup copies of previous versions for development or historical purposes.

 

[Eddie Mason]

Hi Chann,

Many thanks I am really grateful for the advice. The reason I needed the advice was that the end users tend to retain old copies of the front end when I send them an update and occasionally one of these old front ends get copied back in error when the computer has a problem or it gets replaced.

Many thanks again,

Eddie