[AccessD] Source Control
Ryan W
wrwehler at gmail.com
Thu Jun 27 11:08:54 CDT 2019
Well, you can't check in the accdb and have anything like GIT or SVN show
you the difference between versions of forms and such. You can still use
github but you need a way to extract the form code or whatever to make it
usable. These tools do that, apparently. Wondering if they're any better
than my roll-your-own version.
On Thu, Jun 27, 2019 at 10:57 AM Mark Simms via AccessD <
accessd at databaseadvisors.com> wrote:
> What about Github ?
> https://www.softwaretestinghelp.com/version-control-software/
>
> Mark Simms
> marksimms at verizon.net
>
>
> ----- Original Message -----
> From: Ryan W <wrwehler at gmail.com>
> To: Access Developers discussion and problem solving <
> accessd at databaseadvisors.com>
> Sent: Thu, Jun 27, 2019 11:36 am
> Subject: [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. I've been doing it all
> 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 control the tables too ... I guess.
> -
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
> --
> 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