Accde/accdb versions - can you determine if they are the same?

[aytee111]

Is there any way to determine that an accde belongs to a certain accdb? The accde is created for the user and later the developer sneaks in and makes a change which doesn't get into the production version. Can one compare the two databases and know that the "versions" aren't the same, does Access do anything behind the scenes that I can look at?

[ranman256]

i keep the version# on the startup form title bar so this doesnt happen.

[aytee111]

Where do you get the version number from? If it is manually entered, how do you prevent it being left unchanged?

[ranman256]

I set it to the date of my updates yymmdd.hhnn , v161231.1301
make other developers do so too.

[aytee111]

I was looking for an automated way of doing this, not manual - us developers are not to be trusted!

[CJ_London]

I do as ranman does, but it would not stop me making a change to the development version and forgetting to update the version# - or updating the version# and not making a change to the development version for that matter. I store the version number in the db properties rather than hardcoded on a form, in vba or a table. I also store the application generic name there as well (reason is I may have the same app with several clients who all want to call it something different, so I can't rely on the file name)

If in doubt, the development version always wins and the production version is replaced.

One thing that might help is if you open the .accde file properties you will see the creation date. If you are maintaining an archive of earlier versions of the development copy, you may be able to compare this date with the modified date of the development .accdb.

[CJ_London]

if you want automated, create a process to create the .accde using the undocumented syscmd 603 command and include prompts for versions etc. See this link

http://stackoverflow.com/questions/3...vba-syscmd-603

[aytee111]

Thanks for that link. This will definitely be an automated process so tables can be updated to store dates and versions and etc, but I hadn't got as far as getting into the coding yet. The problem is that it can't go into production until it has been tested, so the development version cannot always win. I am trying to plug that hole.

DB Properties, that's a good idea.

I could store the Windows file date created of the accdb in the accde - would that do it do you think? (Still trying to think this thru)

[CJ_London]

I could store the Windows file date created of the accdb in the accde

doubt it, suggest you need the modified date. You start a new project - file created date is populated. 2 weeks later you make some changes and update the version - creation date remains the same.

I advise at the same time you create the accde you archive a copy of the development db (front and backend)

[aytee111]

Yes, modified date would be more accurate.

Thanks for these ideas.