Re: ADODB.Connection object not returning correct ConnectonString
- From: chaosu <chaosu@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 3 Jul 2009 09:14:01 -0700
Hello Elize,
I already find repro. I will discuss the issue with our team. After make
final decision, I will notify you.
Repro is as follow,
set conn=CreateObject("adodb.connection")
connectme="DRIVER={SQL Server};Server=xx;database=master;User
Id=xx;Password=xx"
conn.open connectme
msgbox "display connection string"
msgbox conn.connectionstring
"chaosu" wrote:
Hi Eliz,.
First of all, can you tell me what kind of properties that MSDASQL doesn't
return whereas SQLOLEDB return ?
Tell me the properties and share me the repro, I can help you do thoroughly
investigation on it.
According to the definition of IDataInitialize::GetInitializationString, you
can definitly create or open new connection by using connection string from
one successed connection.
Certainly, you have to pay attention that security information will be lost
in the returned connection string, unless you explicitly insert "Persist
Security Info=TR
UE" into connection string that looks like as follow,
"Provider=SQLOLEDB;Data Source=serverName;"
Initial Catalog=databaseName;
User ID=MyUserID;Password=MyPassword;"Persist Security Info=TR
UE"
Anyway, thanks for your passion to follow up the issue. I'd like to work
with you to resovle the issue.
"Eliz" wrote:
Thanks for your input. I finally got someone at Microsoft to look at the
problem. They could see the problem in my test environment, but they have to
reproduce it in THEIR environment before they can log a bug. They do see the
problem however.
I'll post again as soon as I know the bug number, but essentially, in
Windows 2008, they replaced MDAC with WDAC and the belief is that it is
something to do with that.
"Bob Barrows" wrote:
You're making me go to a web site? Why not just tell me?
OK, I've gone to the forum and found this "It looks like this behavior
is unrelated to 64 bit; theThe same occurs on Windows 2008 32 bit. It
looks like this is just a "Windows 2008 thing". "
It does not appear you are going to get this resolved to your liking.
MSDASQL is deprecated so MS will probably not be interested in hearing
about any bugs with it. You could try calling Product Support, but I
doubt you will get anywhere, along with having to par for the call,
which would normally be free with a confirmed bug report. Sorry.
gdarling -ORCL wrote:
Hi Bob,
The same thing occurs when using the SQL Server driver if that
makes your testing easier :) . See my response in this Oracle forum
post for example output and code:
http://forums.oracle.com/forums/thread.jspa?threadID=920457&tstart=0
Greg
"Bob Barrows" wrote:
Eliz wrote:
connStr = "DRIVER={Oracle in
OraClient10gWin2K8x86};DBQ=ORCL;UID=SCOTT;PWD=TIGER;"
Set conn = CreateObject("ADODB.Connection")
conn.ConnectionString = connStr
MsgBox conn.ConnectionString
conn.Open connStr
'Should NOT return "Provider=MSDASQL.1;"
That's where your thinking is wrong. ADO requires an OLE DB
provider. That is the only way it can make connections. So, when you
do not specify a provider in your connection string, ADO defaults to
the MSDASQL provider (the OLE DB Provider for ODBC).
I cannot run your script since I have no Oracle database, so could
you show us the contents of that MsgBox? I don't see any extended
properties in your supplied connection string so I'm not really sure
what is missing.
--
Microsoft MVP - ASP/ASP.NET - 2004-2007
Please reply to the newsgroup. This email account is my spam trap so
I don't check it very often. If you must reply off-line, then remove
the "NO SPAM"
--
HTH,
Bob Barrows
- Follow-Ups:
- References:
- Prev by Date: Re: Still problems with ADO
- Next by Date: Re: ADODB.Connection object not returning correct ConnectonString
- Previous by thread: Re: ADODB.Connection object not returning correct ConnectonString
- Next by thread: Re: ADODB.Connection object not returning correct ConnectonString
- Index(es):
Relevant Pages
|
