Enumerate ODBC System records

By calling CDatabase::OpenEx(NULL, CDatabase::forceODBCDialog)
you get the ODBC DSN Control panel selection screen thingy to choose from.
That screen has File, System and perhaps more tabs on them
I want to not go through that selection window, instead only enumerate the
System DSNs in my own app.
I know this info is stored in the windows registry, but I'm looking to do
this using the right way: documented API's.
Any idea ?
LisaTake a look at the SQLDataSources API. This will allow you to enumerate the
DSNs.
HTH
--
============
Frank Hickman
NobleSoft, Inc.
============
Replace the _nosp@.m_ with @. to reply.
"Lisa Pearlson" <no@.spam.plz> wrote in message
news:OjuNz$02DHA.1760@.TK2MSFTNGP10.phx.gbl...

quote:

---

> By calling CDatabase::OpenEx(NULL, CDatabase::forceODBCDialog)
> you get the ODBC DSN Control panel selection screen thingy to choose from.
> That screen has File, System and perhaps more tabs on them
> I want to not go through that selection window, instead only enumerate the
> System DSNs in my own app.
> I know this info is stored in the windows registry, but I'm looking to do
> this using the right way: documented API's.
> Any idea ?
> Lisa
>

---

EntMgr "Provider could not be found"

When doing open table-return rows - got the above
message... is this some sort of ODBC problem? thx
I'm having same problem,
"Shelley" wrote:

> When doing open table-return rows - got the above
> message... is this some sort of ODBC problem? thx
>
sql

EntMgr "Provider could not be found"

When doing open table-return rows - got the above
message... is this some sort of ODBC problem? thxI'm having same problem, :(
"Shelley" wrote:
> When doing open table-return rows - got the above
> message... is this some sort of ODBC problem? thx
>

Entity ’ in SQL Server 2000 output

I have an application that queries a SQL Server 2000 db through an ODBC driver on my Win2000 machine.

The DB contains some french text e.g. ltranger stored in a nvarchar column.

When I query the DB the result contains the entity &# 8217; rather than the character itself. I don't want this and it doesn't happen in SQL Server 7.

Tried changing the collation from SQL_Latin1_General_Cp1_CI_AS but with no luck.

Does anyone have experience with this?

ThanksHi,
Did you change collation on the entire dB or on table and column ?
Which collation do you have as standard ?

Regards
Tommy|||Hi,

We've changed the collation of the individual dB/table, but not
the collation of the server (which is still SQL_Latin1_General_CP1_CI_AS), so as not to affect other dBs.

Is it likely to be a collation issue?|||Hi,

I'm not sure about that. I've tried to insert that text into a table with collation SQL_Latin1_General_CP1_CI_AS and the result in query analyzer is correct, have you tried select "column" from "table".
Is the result the same ?
Where did the dB data come from ?
You may check how it's inserted into the dB.

Let me know !

Tommy|||Hi,

Thanks for taking an interest.

The original data is probably generated in some Microsoft applications i.e. Word. I have no control over that.

Yes, the results look okay in query analyser, the problem occurs when I do SQL calls through an ODBC driver from a remote machine.
I don't think it's a driver problem because I get the correct characters when testing on SQL Server 7.

What has changed between 7 and 2000?

Help|||Ok,
That's a tricky one..
One of the things that changed in SQL 2000 is collations (the possibility to set collations on dB, tables and columns not just on the server).
and sometimes just change the collation on the table or columns or only the dB just ain't enough.

Some things you can do is:
Check the application, how/what does it when querying the dB, how do the question look like. (run SQL profiler) if you can't look in the code.

The collation on SQL 7 ?

How did you do the switch from SQL 7 to 2000 ?

Regional settings on the client. (? ? I'm not sure about this)

Anyone else have a succession ?

I can send you a proc that handles collations if you'll like.
Regards
Tommy|||Hi,

Basically we just send an SQLExecute command with a SELECT statement.

Of course I can parse out the & #8217 from the results but surely I shouldn't need to? (And also what about any other entities I may encounter?)

Anyway, thanks for the suggestions

Enter userid and password for the databse (Crystal Reports 10)

Hi,

I have updated crystal reports from version 8 to 10. Updated the datasource, using odbc connection to connect to SQL Server. Reports run fine on my machine. When I run reports on the server I get enter userid and password for the database. Looks like, when I run reports on the server it's caching Server name from my machine. I have clear cache on the server which did not help. I am sending userid and pwd in the URL to Crystal reports. Please let me know, if there is a work around. FYI, reports work fine in production.

Thanks in Advance,
BhavnaDon't check Trusted connection checkbox when setting Datasource location. Unchecking this check box resolved the issue.

-Bhavna