[AccessD] Access and source control

[Arthur Fuller]

Gustav,

I do the same, and I guess most or all of us do. And that's fine insofar as
only one developer is working on a project at any given time. It would be
nice to be able to have a team of developers working on a project, each
member checking out a few objects and all other developers seeing that
those have been checked out. You and I could thus work simultaneously on
different aspects of Project X, then check our objects back in, and if
anything screws up, then we could roll back just that object while
preserving the changes that were successful.

That's one of the many reasons that I'm so taken with Alpha Anywhere. It
stores objects in a granular fashion; any given project might consist of
hundreds of files of various types -- HTML, CSS, JavaScript, A5W
(proprietary), text files, Xbasic modules and function libraries, and
images. The core of the project is a database similar to the database
window in older versions of Access, containing pointers to the actual files
(stored in subdirectories of the project) rather than the files themselves.
This setup makes proper version control a breeze, and ideal for project
develoment by a team.

/Arthur

On Fri, Jan 22, 2016 at 10:12 AM, Gustav Brock <gustav at cactus.dk> wrote:

> Hi Arthur
>
> Neither can I. And even if you could, it would be faster and safer to
> restore the complete file from a zipped copy. That's what I do - zip a
> backup whenever I have done - or plan to start - some major changes. The
> zip gets the current timestamp as part of the filename. Takes very little
> time.
>
> /gustav