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

ADO Connection Open fails under source safe

P: n/a
Hello there

Am having problems with:

Set cnn = New ADODB.Connection
With cnn
.ConnectionString = CurrentProject.Connection
End With

The Open command fails, typically with -2147467259 error, if
application under source safe. If I remove database from source safe
and then run Access down and up again, it works fine. Have code
isolated in test case.

Do I need to use DAO if I use Source Safe?


Oct 11 '06 #1
Share this Question
Share on Google+
2 Replies

P: n/a
I don't see why source safe would make a difference.

I would would looking at code check your references (as compared to the
version that works).
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
Oct 11 '06 #2

P: n/a
Made some changes and then took them out again. What seemed to make
the difference was doing a source safe operation. (Have tried 'Get
Latest Version...' and 'Checkout' on any file to achieve the desired
effect! I am not configured to run 'Get Latest Version' automatically
on login. Prefer to run it explicitly.) This hypothesis explains
previous false dawns I've had.

After actively doing a source safe operation, the original code will
work. If I open up the database when its in source safe and just
execute the code it will not work. Guess I have a workaround now!

My references are, in order:

Visual Basic for Applications
Microsoft Access 11.0 Object Library
Microsoft ActiveX Data Objections 2.8 Library

Environment is Source Safe 6.0d with service pack 6 and Access 2003.

Many Thanks

Oct 12 '06 #3

This discussion thread is closed

Replies have been disabled for this discussion.