From Access 2003 to Access 2007 through Visual SourceSafe 2005

[Davide]

Hi all... I've just uninstalled A2003 and installed A2007 and I've worked
with Access and VSS since 2000, so I've lots of projects under VSS.
Now I'm creating the Access database form an old VSS project with A2007 and
it creates a MDB file instead of an ACCDB file, even though the defalu
version is A2007. However, if I create a new database and I add it to VSS,
A2007 will create an ACCDB file.
I've noticed that my old projects have, into VSS, ACB and ACN subfiles,
while the new project has ACD and ACX files and I've also read that ACB is
for MDB whil ACD is for ACCDB...
So...
How can I convert my old database stored in VSS from MDB to ACCDB, or
better, how can I convert the ACB subfile to a ACD subfile?
Can someboby support me? Thank you in advance!
Davide

 

[Paul Shapiro]

To update a db in SourceSafe from an older Access mdb format to a later mdb
format, I've checked out everything, done the conversion, and then checked
it all back in again. When converting to accdb, you will probably have new
objects that need to be added to SourceSafe. I've never done that conversion
with SourceSafe, so I don't know if there are other issues that will appear
due to the change in the system object naming. I would make a copy of your
current mdb, remove it from sourcesafe, rename it, and then add it as a new
sourcesafe project. Do your testing with that db, and when you are satisfied
with how to proceed, delete the test project from sourcesafe.

A fall-back option is to start a new SourceSafe project with the accdb,
although your code history then gets split between the original mdb project
and the new accdb project.

 

[Albert D. Kallal]

The only way I can see to do this is to simply build your latest mdb version
in 2003, and then move that application into access 2007, and then start a
new project in VSS.

I really don't think it much wise to attempt any other pathway then the
above. You really don't want to start playing around with the source safe
files and attempt to move them between different versions as I don't believe
anyone has any idea as to how well this would work.

You want to take a known working mdb file, and have 2007 convert that mdb to
an accDB. Any issues of VSS should be eliminated during this conversion
process.

Once the application is running in 2007, then at that point I would start a
new source project.

 

[Davide]

that are different in a few onesThank you, Paul.

All you've just written is true and, in fact, I've all done before posting
my question here. I can convert MDB into ACCDB and then add it to the VSS and
everything works perfectly...
The reason because of I've posted the issue here is that working this way
I'll lose all the link between shared objects in different projects.
Actually I've lot of projects, for instance, that are sharing the same
forms, queries, macros and that are different in a few ones. Creating a new
project after having converted anything to ACCDB I'll lose tho opportunity to
modify a shared object once and to have it already done on all the others
projects...

At this point, do you know how to replicate the objects sharing betwenn two
new projects on some objects of them?

Thank you very much again for your support and... Happy new year!
Davide

 

[Davide]

Hi Albert...
Thank you very much for answering my question.

As I wrote above to Paul, everything works perfectely moving any project
form A2003 to A2007 and then starting a new project in VSS...
My only problem is the sharing loss...

Is there any way to replicate the sharing once I've re-added all my projects
after having converted them?

Thank you again for your help!
Happy new year!
Davide

 

[Paul Shapiro]

It's been a while since I was setting up shared objects between Access
databases in SourceSafe projects, but I seem to remember that it's easy to
do in the SourceSafe Explorer. I think you have to delete the objects to be
shared from the new accdb, and then recreate those shared objects in
SourceSafe after adding the accdb project. If the accdb has already been
added to SourceSafe, then you might need to purge the project in the
SourceSafe explorer to completely eliminate those objects after they are
deleted and before adding the shared versions.

I also seem to remember some issues when Access objects are shared between
different Access formats. With some format changes, there are hidden
properties that are either different (like a version number) or that don't
exist in the older format and could be lost when updating the object in the
older project. You could look for these changes before deleting the accdb
objects to be shared by doing a SourceSafe comparison between representative
upgraded objects and the currently shared version in the older projects.

Hi Albert...
Thank you very much for answering my question.

As I wrote above to Paul, everything works perfectely moving any project
form A2003 to A2007 and then starting a new project in VSS...
My only problem is the sharing loss...

Is there any way to replicate the sharing once I've re-added all my
projects
after having converted them?

Thank you again for your help!
Happy new year!
Davide

 

[Davide]

Hi Paul...
Happy new year!!!

It's been a while since I was setting up shared objects between Access
databases in SourceSafe projects, but I seem to remember that it's easy to
do in the SourceSafe Explorer. I think you have to delete the objects to be
shared from the new accdb, and then recreate those shared objects in
SourceSafe after adding the accdb project. If the accdb has already been
added to SourceSafe, then you might need to purge the project in the
SourceSafe explorer to completely eliminate those objects after they are
deleted and before adding the shared versions.

All you've just written is true! I've already tried before asking here and
everything works. The problem is that my projects are lots adn the shared
objects are much more... So doing everything manually through the VSS
interface is very difficult and also error-prone.
However, if this is the only way...

Thank you again for your help!