I am involved in writing a lot of VB5 code for an application that uses
Crystal Reports as the report engine. I've been told by the Crystal
developer that CR needs a DSN (it can't be DSN-less) to be created in order
for crystal to access the ODBC data source.

using VB (and RDO) I could call a built-in function to register a DSN.
However, I believe this only creates a "User DSN", not a "SYSTEM DSN". I may
need to use a Win32API call to create a system DSN.

Our app will be running on Windows 95/Windows NT 4 workstation.

Can somebody tell me if A) CR can use DSN-less connections (via an .INI
file?), or if we use DSNs, does it have to be a SYSTEM DSN or will a USER
DSN do?

Thanks.

--
Alastair Cameron

I am going under the assumption you are using MS SQL Server for the database.
If you are using the Professional version of Crystal Reports, you can use Native
SQL Server driver instead of the ODBC driver.  This will allow you to create a
DSN-less connection.

If you do decide to go and use ODBC, Crystal can use either System or User
datasources.  Crystal cannot use File datasources.

--
Sincerely,
Brian Dong

To reply, remove nospam from the address.