[AccessD] Source Code Control

Just checked -
http://www.microsoft.com/downloads/details.aspx?familyid=2ea45ff4-a916-48c5-8f84-44b91fa774bc&displaylang=en -
it worked here well with both MS Access 2003 and MS Access XP.

But it is still unclear will it work OK on a pure MS Office XP system
or not because they say it needs MS Office 2003 SP1 installed.

I did have MS Office 2003 SP1 installed before I installed and run this
add-in.

It may happen MS Office 2003 SP1 patches some system/shared files used by
both MS Office XP and MS Office 2003.

And I guess MS Office 2003 SP1 can't be installed for MS Office XP.
Then this add-in may not work properly.

Shamil

----- Original Message ----- 
From: "Charlotte Foust" <cfoust at infostatsystems.com>
To: "Access Developers discussion and problem solving"
<accessd at databaseadvisors.com>
Sent: Monday, January 16, 2006 8:59 PM
Subject: Re: [AccessD] Source Code Control


> I should think so.  Both XP and 2003 are based on VB6, not VS.Net, so
> you should be able to use it.  Worth a try anyhow.  We're still using
> Access XP to maintain our current generation apps, so I can't test it.
>
> Charlotte Foust
>
>
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Dan Waters
> Sent: Monday, January 16, 2006 9:20 AM
> To: 'Access Developers discussion and problem solving'
> Subject: Re: [AccessD] Source Code Control
>
>
> Charlotte,
>
> I've seen where I can download this add-in for Access 2003, but I was
> wondering if the add-in can also be used with Access XP?
>
> Dan
>
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Charlotte
> Foust
> Sent: Monday, January 16, 2006 10:41 AM
> To: Access Developers discussion and problem solving
> Subject: Re: [AccessD] Source Code Control
>
> I don't know what you mean, Josh, but I suspect you haven't had actual
> experience with SourceSafe.  We use SourceSafe with Access and with
> VB.Net and have no problems comparing versions.  With Access, you do
> need the add-in that allows you to work with Source Safe from within
> Access (comes with the ODE, if I remember correctly).  This maintains
> each object as a separate sourcesafe file, not the entire database.  Nor
> have we had the corruption issues you describe.  ANY file can and will
> corrupt.  It isn't peculiar to any particular product or program.
>
> Charlotte Foust
>
>
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Josh
> McFarlane
> Sent: Saturday, January 14, 2006 2:35 PM
> To: Access Developers discussion and problem solving
> Subject: Re: [AccessD] Source Code Control
>
>
> On 1/14/06, Dan Waters <dwaters at usinternet.com> wrote:
> > Has anyone used a program called Vault from Sourcegear, or Perforce,
> > while programming in Access?  If it worked, was it useful?
>
> Dan,
>
> For Access IIRC, source control will lose one of it's most important
> featuers (diff'ing) with Access because Access is stored as a binary
> file.
>
> That said, I've used 3 different source control programs while working
> on C++ coding.
>
> Visual Source-Safe: Steer clear of this one - It's outdated and has a
> high corruption rate on the source control database.
>
> CVS: Open-source, widely used, and widely tested. Nice for single-file
> verisoning. Made for Unix but NT versions are also available
>
> Subversion: Also open source, this is what we currently use in shop. It
> maintains versioning on a per-repository basis rather than a per-file
> basis. Very very nice freeware client called TortioseSVN. Was fairly
> easy to set up also. Also tracks file renames, directory changes, and
> other meta information. Allows you to also add a meta-tag to track
> changes due to bug-fixes from bug-tracking software, etc.
>
> As a whole, it'd work great for a backup / revision system as long as
> you made sure that when you checked in files you comment what changed.
>
> If you try out Vault or Perforce, let me know what you think.
>
> --
> Josh McFarlane
> -- 
> 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
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com