M
Michael
Office 2003 (same behavior with Office 2007 with Access Developer Extensions)
SourceSafe 6.0d
Access Source Control for Access 2003
SourceSafe has been setup for about three years now and we have been using
it to manage the Access objects. Recently I tried to add a new database to
SourceSafe and was unable to do so. What happens is this.
- I open the relevant Access database
- I select "Add to SourceSafe" from the menu
- I am prompted that the database will need to be closed first
- I click Yes
The problem occurs at this point as the database is not close, I still see
each of the objects in the database window.
Clearly something has changed but it has been so long since we have added a
database I don't know where to begin to identify what that might be.
I know that our version of SourceSafe is old, but it is patched to as recent
as I'm aware (6.0d).
Office is updated per Microsoft Update.
I reinstalled the Access Source Control add-in.
But what really baffles me is that this happens with both Access 2003 and
Access 2007. I even created a new repository thinking that perhaps the
repository is somehow causing this issue.
Help Please
thanks
Michael
SourceSafe 6.0d
Access Source Control for Access 2003
SourceSafe has been setup for about three years now and we have been using
it to manage the Access objects. Recently I tried to add a new database to
SourceSafe and was unable to do so. What happens is this.
- I open the relevant Access database
- I select "Add to SourceSafe" from the menu
- I am prompted that the database will need to be closed first
- I click Yes
The problem occurs at this point as the database is not close, I still see
each of the objects in the database window.
Clearly something has changed but it has been so long since we have added a
database I don't know where to begin to identify what that might be.
I know that our version of SourceSafe is old, but it is patched to as recent
as I'm aware (6.0d).
Office is updated per Microsoft Update.
I reinstalled the Access Source Control add-in.
But what really baffles me is that this happens with both Access 2003 and
Access 2007. I even created a new repository thinking that perhaps the
repository is somehow causing this issue.
Help Please
thanks
Michael