By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
459,282 Members | 1,587 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 459,282 IT Pros & Developers. It's quick & easy.

Upsizing Access 2003 db with SourceSafe 6.0d to SQL Server 2005 - Crashes

P: n/a
I have happily been using Access 2003 sp1 with SourceSafe 6.0d (build
31222) for two years. However, application database is being upsized
to SQL Server 2005, currently sp2 Developer Edition. I can use Source
Safe from the SQL Server database though there were warnings about
encoding. However, Access crashes with 'Microsoft Office Access has
encountered a problem and needs to close' if I try to relink my
checked out tables to SQL Server while Access is linked to Source Safe
using an upsizing utility. If I remove the database from Source Safe
I can relink the tables to SQL Server fine. However, if I try to add
the relinked database to a new Source Safe project Access again
crashes. I get none of the usual prompts about the new Source Safe
project nor adding all objects to Source Safe. The file name given
in the database properties does match the actual file name. OS is XP
Pro sp2. I can relink the Northwind database and add it to Source
Safe. A couple of my tables have spaces in their tables names but
otherwise all are standard alphanumerics. Any ideas? Many Thanks.

Sep 26 '07 #1
Share this Question
Share on Google+
2 Replies


P: n/a
On Wed, 26 Sep 2007 09:17:50 -0000, breadon <br********@yahoo.co.uk>
wrote:

When I read the list of exceptions from MSFT as to when it was safe to
use SS with MDB's, I immediately decided against it. So in our
company we check in/out the entire binary object, not individual
objects. Yes, it slows us down sometimes, and I hate to have to put
"work integration" on our estimates, but it avoids untold other
issues.

-Tom.

>I have happily been using Access 2003 sp1 with SourceSafe 6.0d (build
31222) for two years. However, application database is being upsized
to SQL Server 2005, currently sp2 Developer Edition. I can use Source
Safe from the SQL Server database though there were warnings about
encoding. However, Access crashes with 'Microsoft Office Access has
encountered a problem and needs to close' if I try to relink my
checked out tables to SQL Server while Access is linked to Source Safe
using an upsizing utility. If I remove the database from Source Safe
I can relink the tables to SQL Server fine. However, if I try to add
the relinked database to a new Source Safe project Access again
crashes. I get none of the usual prompts about the new Source Safe
project nor adding all objects to Source Safe. The file name given
in the database properties does match the actual file name. OS is XP
Pro sp2. I can relink the Northwind database and add it to Source
Safe. A couple of my tables have spaces in their tables names but
otherwise all are standard alphanumerics. Any ideas? Many Thanks.
Sep 27 '07 #2

P: n/a
Thanks Tom. I appreciate that you do not use source safe with
Access. Can you point me at the reference you are quoting?

I have sorted out my immediate problem. There were a handful of
queries that crashed Access until I reworked them for sql server. I
was then able to put the Access database in to Source Safe. It was
difficult to make source safe + access workable when I first started
using it. However, I had twenty years of developing under source code
control and was very reluctant to give it up. I had a little previous
experience of Source Safe and knew its limitations from bitter
experience - its not my preferred source code control system. That
said, if no one uses Access with source code control, it will never
get better .....

Regards
Breadon

Sep 27 '07 #3

This discussion thread is closed

Replies have been disabled for this discussion.