MS Access and SourceSafe: How to sync local files with Accees objects

Y

Yarik

This is about an ADP project (Access 2003) integrated with SourceSafe.

Let's say there is a form in the ADP project, which corresponds to
some .FRM file in the SourceSafe repository (let's call it "master
source file") and to some local .FRM file (let's call it "local source
file"):

Form <---> Local Source File <---> Master Source File

When I check the form out (without making any changes yet) the Local
Source File is "in sync" with the Form; that is, its contents reflects
the current state of the Form.

Now, when I make some change to the Form and save it, the
corresponding Local Source File is no longer "in sync" with the Form.

I know at least two ways to bring the Local Source File back "in sync"
with the Form:

(1) Try to check the Form in

(2) Try to get version history for the Form

Now, the question is: when I have multiple Access objects (e.g.
multiple forms) checked out and changed, is there any easy way to
"sync" ALL of them with their corresponding local source files without
checking in? Selecting objects one-by-one and trying to get version
history for each of them does not qualify as an easy way - it's too
laborous (especially when objects of different types have been checked
out and modified).

I've noticed that sometimes, when I try to get the latest versions of
all the objects in an Access project, Access kind of "stumbles" on
each checked-out object that has been modified (asking me whether I
want overwrite this object, leave it alone, or merge it). This is
probably some bug in Access, but this bug has a very interesting side-
effect: whenever this happens, the local source files of those objects
appear to be "in sync"! So I would be happy to use this bug's side-
effect to "sync" all the local file, but the problem is - I cannot
reproduce this problem at will... :-(

Any help would be greatly appreciated.
 
?

????? ?????????

Yarik said:
This is about an ADP project (Access 2003) integrated with SourceSafe.

Let's say there is a form in the ADP project, which corresponds to
some .FRM file in the SourceSafe repository (let's call it "master
source file") and to some local .FRM file (let's call it "local source
file"):

Form <---> Local Source File <---> Master Source File

When I check the form out (without making any changes yet) the Local
Source File is "in sync" with the Form; that is, its contents reflects
the current state of the Form.

Now, when I make some change to the Form and save it, the
corresponding Local Source File is no longer "in sync" with the Form.

I know at least two ways to bring the Local Source File back "in sync"
with the Form:

(1) Try to check the Form in

(2) Try to get version history for the Form

Now, the question is: when I have multiple Access objects (e.g.
multiple forms) checked out and changed, is there any easy way to
"sync" ALL of them with their corresponding local source files without
checking in? Selecting objects one-by-one and trying to get version
history for each of them does not qualify as an easy way - it's too
laborous (especially when objects of different types have been checked
out and modified).

I've noticed that sometimes, when I try to get the latest versions of
all the objects in an Access project, Access kind of "stumbles" on
each checked-out object that has been modified (asking me whether I
want overwrite this object, leave it alone, or merge it). This is
probably some bug in Access, but this bug has a very interesting side-
effect: whenever this happens, the local source files of those objects
appear to be "in sync"! So I would be happy to use this bug's side-
effect to "sync" all the local file, but the problem is - I cannot
reproduce this problem at will... :-(

Any help would be greatly appreciated.
 
Ð

жанна Ñ€Ñбчикова

Yarik said:
This is about an ADP project (Access 2003) integrated with SourceSafe.

Let's say there is a form in the ADP project, which corresponds to
some .FRM file in the SourceSafe repository (let's call it "master
source file") and to some local .FRM file (let's call it "local source
file"):

Form <---> Local Source File <---> Master Source File

When I check the form out (without making any changes yet) the Local
Source File is "in sync" with the Form; that is, its contents reflects
the current state of the Form.

Now, when I make some change to the Form and save it, the
corresponding Local Source File is no longer "in sync" with the Form.

I know at least two ways to bring the Local Source File back "in sync"
with the Form:

(1) Try to check the Form in

(2) Try to get version history for the Form

Now, the question is: when I have multiple Access objects (e.g.
multiple forms) checked out and changed, is there any easy way to
"sync" ALL of them with their corresponding local source files without
checking in? Selecting objects one-by-one and trying to get version
history for each of them does not qualify as an easy way - it's too
laborous (especially when objects of different types have been checked
out and modified).

I've noticed that sometimes, when I try to get the latest versions of
all the objects in an Access project, Access kind of "stumbles" on
each checked-out object that has been modified (asking me whether I
want overwrite this object, leave it alone, or merge it). This is
probably some bug in Access, but this bug has a very interesting side-
effect: whenever this happens, the local source files of those objects
appear to be "in sync"! So I would be happy to use this bug's side-
effect to "sync" all the local file, but the problem is - I cannot
reproduce this problem at will... :-(

Any help would be greatly appreciated.
 
Y

Yarik

I just usually take a copy of the whole project twice a day and I call
it myFile_20080818.adp, etc
this way- I can revert to the old copy of that form, etc

I think that is definitely simpler-- I've just never gotten what I
wanted out of SourceSafe-- unless I was using DreamWeaver.

Sorry, but not using SourceSafe is not an option: there are multiple
developers working on the project.

MS Access' integration with SourceSafe isn't perfect, but it's good
enough to be used in practice, IMHO....
 
R

Roger Carlson

I'm not sure what the actual original question was, but you need a couple of
pieces to make SourceSafe work with Access. First, of course, you need
SourceSafe. Then you need the Office Developer's Toolkit (it's called
different things in different versions of Access).

Here are a couple of links that should help:
http://www.microsoft.com/downloads/...f4-a916-48c5-8f84-44b91fa774bc&displaylang=en
http://support.microsoft.com/kb/837136/en-us


--
--Roger Carlson
MS Access MVP
Access Database Samples: www.rogersaccesslibrary.com
Want answers to your Access questions in your Email?
Free subscription:
http://peach.ease.lsoft.com/scripts/wa.exe?SUBED1=ACCESS-L

I just usually take a copy of the whole project twice a day and I call
it myFile_20080818.adp, etc
this way- I can revert to the old copy of that form, etc

I think that is definitely simpler-- I've just never gotten what I
wanted out of SourceSafe-- unless I was using DreamWeaver.

Sorry, but not using SourceSafe is not an option: there are multiple
developers working on the project.

MS Access' integration with SourceSafe isn't perfect, but it's good
enough to be used in practice, IMHO....
 
R

ramonet

Yarik said:
This is about an ADP project (Access 2003) integrated with SourceSafe.

Let's say there is a form in the ADP project, which corresponds to
some .FRM file in the SourceSafe repository (let's call it "master
source file") and to some local .FRM file (let's call it "local source
file"):

Form <---> Local Source File <---> Master Source File

When I check the form out (without making any changes yet) the Local
Source File is "in sync" with the Form; that is, its contents reflects
the current state of the Form.

Now, when I make some change to the Form and save it, the
corresponding Local Source File is no longer "in sync" with the Form.

I know at least two ways to bring the Local Source File back "in sync"
with the Form:

(1) Try to check the Form in

(2) Try to get version history for the Form

Now, the question is: when I have multiple Access objects (e.g.
multiple forms) checked out and changed, is there any easy way to
"sync" ALL of them with their corresponding local source files without
checking in? Selecting objects one-by-one and trying to get version
history for each of them does not qualify as an easy way - it's too
laborous (especially when objects of different types have been checked
out and modified).

I've noticed that sometimes, when I try to get the latest versions of
all the objects in an Access project, Access kind of "stumbles" on
each checked-out object that has been modified (asking me whether I
want overwrite this object, leave it alone, or merge it). This is
probably some bug in Access, but this bug has a very interesting side-
effect: whenever this happens, the local source files of those objects
appear to be "in sync"! So I would be happy to use this bug's side-
effect to "sync" all the local file, but the problem is - I cannot
reproduce this problem at will... :-(

Any help would be greatly appreciated.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top