Access2k3 SourceSafe Add-In doesn't work - HELP!

[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

 

[Paul Shapiro]

You didn't mention, but I assume you're running Access 2003? The SourceSafe
add-ins are version-specific. What version format is the db you're trying to
add?

You were adding the FE to SourceSafe, right? Did you first make sure it
compiles? If not, you should fix that first. If it compiles and adding to
SourceSafe still fails, try creating a new blank db and importing everything
from the existing db. If there's a corrupted object, the SourceSafe addin
could choke.

Last option might be to use the undocumented Application.SaveAsText function
in code of your own that loops through the Access objects. This function is
what the SourceSafe add-in uses to create a text representation of each
object. Once you have a folder of text objects, you could add that to
SourceSafe. It wouldn't integrate with Access, but you could use
SourceSafe's search functions.

 

[teddysnips]

You didn't mention, but I assume you're running Access 2003? The SourceSafe
add-ins are version-specific. What version format is the db you're trying to
add?

You're right - Access2k3

You were adding the FE to SourceSafe, right? Did you first make sure it
compiles? If not, you should fix that first. If it compiles and adding to
SourceSafe still fails, try creating a new blank db and importing everything
from the existing db. If there's a corrupted object, the SourceSafe addin
could choke.

Okay, I've tried this. The version did compile, but having compiled
and saved it another weirdness reared its head - when I tried to "Add
Database to SourceSafe" it told me, as it always does, that "The
database must be closed..." and it asked me if I wanted Access to
close this database. I clicked "Yes", but the database didn't close!
It then showed the SourceSafe logon and I logged in, but nothing was
added.

So I created a new, blank database and tried adding all the objects.
Exactly the same problem - it compiled ok, but wouldn't add to
SourceSafe. I also have Access 2000 and so I tried creating a 2k
version - exactly the same problem (though I had to comment out large
chunks of the code that wouldn't compile).

So I'm pretty mystified. I'll give the "SaveAsText" function a go,
but it's a RRPITA.

Thanks

Edward

 

[Guest]

You're right - Access2k3


Okay, I've tried this. The version did compile, but having compiled
and saved it another weirdness reared its head - when I tried to "Add
Database to SourceSafe" it told me, as it always does, that "The
database must be closed..." and it asked me if I wanted Access to
close this database. I clicked "Yes", but the database didn't close!
It then showed the SourceSafe logon and I logged in, but nothing was
added.

So I created a new, blank database and tried adding all the objects.
Exactly the same problem - it compiled ok, but wouldn't add to
SourceSafe. I also have Access 2000 and so I tried creating a 2k
version - exactly the same problem (though I had to comment out large
chunks of the code that wouldn't compile).

So I'm pretty mystified. I'll give the "SaveAsText" function a go,
but it's a RRPITA.

Thanks

Edward

 

[teddysnips]

<[email protected]> skrev i meddelelsen







- Show quoted text -

?

 

[Paul Shapiro]

Before resorting to SaveAsText, you could try importing only some of the FE
objects into a new db, and see if that one can be added to SourceSafe. Maybe
start with just all the tables, which are table links anyway. Then try all
the queries, etc. Maybe most of the objects are ok and you can narrow down
the corrupted one(s).
Paul Shapiro

<[email protected]> skrev i
meddelelsen







- Show quoted text -

?