Y
Yarik
Hello everyone!
We have an ADP project created using Access 2000. This project is
under source control (using the Access' standard add-on that
integrates Access with SourceSafe).
Now we use Access 2003 to work with this project. Everything seems to
be working okay, including integration with source control. When this
ADP file is opened by Access 2003, it says that the project has "2000
file format".
Which brings up two questions:
(1) What are the strongest reasons to upgrade "file format" of this
project from 2000 to 2003?
For example, within last few months or so, we saw Access 2003 fail
without any obvious reason quite a few times. Usually, re-opening of
the ADP file did not help in such situations, but complete
"restoration" of the project file from source control always helped.
Is it possible that at least some of those unexplained and random
failures were actually caused by some problems with "2000 file format"
being used with Access 2003?
(2) How exactly can I perform the conversion from 2000 file format to
2003 one without losing "connection" to the source control?
For example, when I try to convert the ADP file using
Tools > Database Utilites > Convert Project > To 2002-2003 file
format
menu command, I successfully get a new ADP file in new format.
However, this procedure does not seem to affect in any way the actual
"project sources" in SourceSafe repository, so when I recreate the
project from SourceSafe repository, I'm getting an ADP file in old,
2000 file format again.
FWIW, I did not try (yet) to perform this conversion procedure "in
place" - i.e. without creating a new ADP file. I am not even sure that
it's technically possible, but the main reason of my hesitation is
that I want to keep this project's sources in SourceSafe repository
(preserving all the history), and I don't want to take any chances.
Should I try to do that "in place" conversion, or it won't help
either?
Any help would be greatly appreciated!
We have an ADP project created using Access 2000. This project is
under source control (using the Access' standard add-on that
integrates Access with SourceSafe).
Now we use Access 2003 to work with this project. Everything seems to
be working okay, including integration with source control. When this
ADP file is opened by Access 2003, it says that the project has "2000
file format".
Which brings up two questions:
(1) What are the strongest reasons to upgrade "file format" of this
project from 2000 to 2003?
For example, within last few months or so, we saw Access 2003 fail
without any obvious reason quite a few times. Usually, re-opening of
the ADP file did not help in such situations, but complete
"restoration" of the project file from source control always helped.
Is it possible that at least some of those unexplained and random
failures were actually caused by some problems with "2000 file format"
being used with Access 2003?
(2) How exactly can I perform the conversion from 2000 file format to
2003 one without losing "connection" to the source control?
For example, when I try to convert the ADP file using
Tools > Database Utilites > Convert Project > To 2002-2003 file
format
menu command, I successfully get a new ADP file in new format.
However, this procedure does not seem to affect in any way the actual
"project sources" in SourceSafe repository, so when I recreate the
project from SourceSafe repository, I'm getting an ADP file in old,
2000 file format again.
FWIW, I did not try (yet) to perform this conversion procedure "in
place" - i.e. without creating a new ADP file. I am not even sure that
it's technically possible, but the main reason of my hesitation is
that I want to keep this project's sources in SourceSafe repository
(preserving all the history), and I don't want to take any chances.
Should I try to do that "in place" conversion, or it won't help
either?
Any help would be greatly appreciated!