Re: ADO OpenSchema( adSchemaPrimaryKeys , ...)



Pete d'Oronzio [pdmagic] wrote:
Now this is strange. I've just tried this on my work machine and
now get correct results:
ADO Version 2.8
Test dbo TestReport ReportID 3 PKTestConstraint
Test dbo TestReport UserGroupID 1 PKTestConstraint
Test dbo TestReport UserID 2 PKTestConstraint

I have no explanation for this, except that I need to check the ADO
version on my home machine.

Yup - strange.

All of Our test machines both report MDAC 2.8 SP1 (On Windows XP SP2)

My bad: my home machine has SQL 2000 on it. I was confused because I had
installed the SQL 2005 client tools and was using SSMS to interface with the
database engine instead of Enterprise Manager.

When I test against a SQL 2000 database at work, I get the results you get

So the issue seems to be resolved in SQL 2005.
Can you upgrade to SQL 2005? What SP version of SQL 2000 are you running?
The version at work is SP3a. SP4 is available. Does the problem occur with
SP4? I am unable to test it.

--
Microsoft MVP - ASP/ASP.NET
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"


.



Relevant Pages

  • Re: ADO OpenSchema( adSchemaPrimaryKeys , ...)
    ... ADO reports incorrect columns when using OpenSchema( ... Test dbo TestReport UserGroupID 1 PKTestConstraint ... Please reply to the newsgroup. ...
    (microsoft.public.data.ado)
  • Re: ADO OpenSchema( adSchemaPrimaryKeys , ...)
    ... Test dbo TestReport UserGroupID 1 PKTestConstraint ... ADO version on my home machine. ... So the issue seems to be resolved in SQL 2005. ...
    (microsoft.public.data.ado)
  • Re: ADO OpenSchema( adSchemaPrimaryKeys , ...)
    ... Test dbo TestReport UserGroupID 1 PKTestConstraint ... Test dbo TestReport UserID 2 PKTestConstraint ... I have no explanation for this, except that I need to check the ADO ...
    (microsoft.public.data.ado)