[AccessD] Source Control

Ryan W wrwehler at gmail.com
Thu Jun 27 12:50:12 CDT 2019

That’s what I do as well. I’d just like to be able to “diff” code sometimes and it makes it  a pain to do. 

Sent from my iPhone

> On Jun 27, 2019, at 12:41 PM, Gustav Brock <gustav at cactus.dk> wrote:
> Hi Ryan
> I gave up on that. No matter what, it would anyway be partial as system tables and database properties could/will change.
> After any major or important change, I simply create a zip of the database and rename it to include the date and time. This way it is simple and non-destructive to pull a previous version and copy or study what you may need.
> The zips are stored on our replicated file server having 2 x 2 backups. Nice and safe.
> /gustav
> -----Oprindelig meddelelse-----
> Fra: AccessD <accessd-bounces at databaseadvisors.com> På vegne af Ryan W
> Sendt: 27. juni 2019 17:35
> Til: Access Developers discussion and problem solving <accessd at databaseadvisors.com>
> Emne: [AccessD] Source Control
> Have any of you used Ivercy (https://www.ivercy.com/Download) Or Oasis-SVN ( https://dev2dev.de/index.php?option=com_content&view=article&id=44&Itemid=260&lang=en
> )
> For source control? These look like they'll do form code, tables, etc.  I know MS used to have some source control available.  All I've been doing is making sure I have stable accdb files, and if I do any large code overhaul I have a function that runs DoCmd.TransferText on all the forms to get the code so I can run it through my GIT repo.
> But it would be nice to version control the tables too... I guess. 
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com

More information about the AccessD mailing list