I hope that someone may shed some light on why I am having difficulties.

Under Visual Basic 6 Enterprise, I opened Visual Basic project and created a
standard EXE project.  I added a Data Environment.  I chose "Microsoft OLE
DB Provider for SQL Server" as my provider.  I selected the Northwind
database.  I verified the connection via "Test Connection".

I used Data View to verify that the database was there and it was.  The
tables folder was there, however, there were tables to expand.  I tried the
same thing with another SQL Database and had the same results.

I repeated the above steps, except this time I chose "Microsoft Jet 4.0 OLE
DB Provider" instead for an Access database.  I was able to view the tables.

I could also view the SQL Server 2000 tables via SQL Server Enterprise
Manager, so I know that the SQL Server database and tables exist.

My question is why can't I see the SQL Server 2000 tables using "Microsoft
OLE DB Provider for SQL Server" as my provider?  And what can I do to make
it work?

Could this be a configuration problem?  I was able to view the SQL Server
2000 databases and tables with the "Microsoft OLE DB Provider for SQL
 Server" working on another system that was running under Windows NT 4.0 SP
6 but DID NOT have Commerce Server 2000 installed.

This is the configuration for my "problem" machine:

Windows 2000 Server SP 1
 IIS 5.0
Windows 2000 Hot fixes
Visual InterDev 6 Enterprise SP 5
Visual Basic 6
 Add-In Manager
  Component Services Add-In for VB 5.0/6.0
  VB 6 Data Object Wizard
  Visual Component Manager 6.0
 References
  Visual Basic for Applications
  Visual Basic runtime objects and procedures
  Visual Basic objects and procedures
  OLE Automation
  Microsoft Data Environment Instance 1.0 (SP4)
  Microsoft ActiveX Data Objects 2.5 Library

SQL Server 2000 - Standard Edition
 Mixed Mode Authentication
MDAC 2.6
Commerce Server 2000
IE 5.5

For those who are willing to respond to my post via the newsgroup, I would
appreciate it greatly if you could e-mail me as well :>).

Best regards,

Just erase the GETRIDOF in my e-mail address to reach me.

Post your connectionstring and/or connectivity code....

BTW:  You're probably going to get chewed-on by others about cross-posting
this to multiple newsgroups, it's considered bad netiquette.
--
Patrick Logan, MCSD

Opinions expressed are my own and not necessarily those of my employer.

Patrick,

Thank you for your response!

To all the reader, please accept my humble apology for the netiquette
misstep.

Here is the Connection String:
Provider=SQLOLEDB.1;Password=pw;Persist Security Info=True;User
ID=sa;Initial Catalog=Northwind;Data Source=CS2K

gymarque

Strange, I duplicated your steps and it worked here.  I'll keep plugging
away at it...

--
Patrick Logan, MCSD

Opinions expressed are my own and not necessarily those of my employer.

Check and make sure the version for your SQLOLEDB is the latest. and matches
that of the server.