T
teddysnips
I've been asked by a client to upsize his home-made database to SQL
Server. The client has no training in database design or application
development, and unfortunately he's living proof that a little
knowledge is a dangerous thing. The actual application isn't that bad
(at least he's split it into FE/BE) and the table names are reasonably
ok, but a lot of the column names are just plain wrong, full of
spaces, "illegal" characters such as ellipses, ampersands and question
marks etc.
I plan to use the upsizing wizard to script the new database, and then
use DTS to import the data (the upsizing wizard barfs over some of the
tables which have gash data).
However, because the upsizing process will rename quite a number of
columns, this will break the FE, so I need to do a deskcheck to see
where these columns are referenced. The "Documenter" tool generated a
7,000 page report which is just a total chocolate kettle as far as I'm
concerned, but in the past I've used SourceSafe to look for column
names (the text search works fine for this).
So I downloaded the Access 2003 SourceSafe Add-In and attempted to add
the DB to SourceSafe. It appeared to go through the right motions -
prompted me for a login to the SourceSafe database, etc. However, it
didn't then do much, and when I tried to check the app out of SS it
tells me:
"Cannot create a new MS Access database from this source code control
project. It contains neither a Data and Misc. Objects file nor a
database name file."
Sure enough, it's created the Project folder in SourceSafe but it's
empty.
Anyone any idea what's going on?
Thanks
Edward
Server. The client has no training in database design or application
development, and unfortunately he's living proof that a little
knowledge is a dangerous thing. The actual application isn't that bad
(at least he's split it into FE/BE) and the table names are reasonably
ok, but a lot of the column names are just plain wrong, full of
spaces, "illegal" characters such as ellipses, ampersands and question
marks etc.
I plan to use the upsizing wizard to script the new database, and then
use DTS to import the data (the upsizing wizard barfs over some of the
tables which have gash data).
However, because the upsizing process will rename quite a number of
columns, this will break the FE, so I need to do a deskcheck to see
where these columns are referenced. The "Documenter" tool generated a
7,000 page report which is just a total chocolate kettle as far as I'm
concerned, but in the past I've used SourceSafe to look for column
names (the text search works fine for this).
So I downloaded the Access 2003 SourceSafe Add-In and attempted to add
the DB to SourceSafe. It appeared to go through the right motions -
prompted me for a login to the SourceSafe database, etc. However, it
didn't then do much, and when I tried to check the app out of SS it
tells me:
"Cannot create a new MS Access database from this source code control
project. It contains neither a Data and Misc. Objects file nor a
database name file."
Sure enough, it's created the Project folder in SourceSafe but it's
empty.
Anyone any idea what's going on?
Thanks
Edward