We used to have several accdb FEs with a sql server BE.
I don't have the exact count, but something between 50 to 70 PCs, less or more.
When we had a change in the database, we opened a version up form and inserted the changes as new records.
After update event of the form issued a new version No based on a certain rule and copied the new FE to a shared folder.
Each PC had a small accdb used as a starter. On launch, the starter copied the FE from the shared folder (if there was a new version) and launched the new version.
The launched FE, checked the starter version, closed it, and if necessary, copied the new version of the starter from the shared folder.
The only manual step for a new version for us was adding a new record to the versions table (via its form)
Since the FE has changed to accde, there are more steps that should be done manually.
The nightmare is saving the database as accde in two bitness.
And since a PC can not have two different bitness of Office, we have to use memory sticks, search a PC with 32 bit office that's available and not used and save the FE as 32 bit accde, bring it back and copy it to shared folder.
Now my questions:
How do you issue new versions of accde files?
Is there any way to automate saving accde in two different bitness?
Is there any way to save a accdb as accde in vba?
Any kind of advice or any kind of info that you think may be a hint is much appreciated.
I don't have the exact count, but something between 50 to 70 PCs, less or more.
When we had a change in the database, we opened a version up form and inserted the changes as new records.
After update event of the form issued a new version No based on a certain rule and copied the new FE to a shared folder.
Each PC had a small accdb used as a starter. On launch, the starter copied the FE from the shared folder (if there was a new version) and launched the new version.
The launched FE, checked the starter version, closed it, and if necessary, copied the new version of the starter from the shared folder.
The only manual step for a new version for us was adding a new record to the versions table (via its form)
Since the FE has changed to accde, there are more steps that should be done manually.
The nightmare is saving the database as accde in two bitness.
And since a PC can not have two different bitness of Office, we have to use memory sticks, search a PC with 32 bit office that's available and not used and save the FE as 32 bit accde, bring it back and copy it to shared folder.
Now my questions:
How do you issue new versions of accde files?
Is there any way to automate saving accde in two different bitness?
Is there any way to save a accdb as accde in vba?
Any kind of advice or any kind of info that you think may be a hint is much appreciated.
Last edited: