SQL ODBC Connection not finding database tables

[susiesunshine]

I have created a SQL ODBC Connection to a database, which tests successfully. However, when I try to create a report, Crystal doesn't find the database when I click on the ODBC connection. When I select the ODBC, it returns "...no items found...". I have Crystal 8. The database is HP Systems Insight Manager. Do I need to upgrade something in Crystal?

 

[MJRBIM]

Oldest version I'm running is 8.5....but check the OPTIONS box on the data explorer.

Make sure that the items you want to show (eg. Table, Views, etc.) are checked.

 

[SQLBill]

Do you have access to the database? The ODBC connects to the SERVER and not the database(s).

When you click on the ODBC connection, does it ask for a login/password? If so, enter both BUT DO NOT YET HIT OK OR ENTER. Then click on the Option button. Make sure the proper database is shown in the database text box.

-SQLBill

 

[susiesunshine]

I checked under Options and Tables, Views are selected. I can get to the server, then I can select the table I am looking for as the default. The ODBC connection uses my NT login/pw for authentification. Am I missing a data dictionary? or maybe something missing from the database itself?

 

[SQLBill]

So, you select the database button, and in the ODBC window, you select your database connection. When that expands you see the tables. Correct?

Then you select the table you want and click on the Add button.

Then what happens?

-SQLBill

 

[ZombyWoof]

I'm having the exact same problem except it's with a Visual Studio created dataset resulting in an XSD file that doesn't get read by the Field Explorer -> Database Expert window. It sees the XSD file but won't return any of the elements to drag and drop to the CR designer.

---That's the short version above. Here's the long version for more detail. ----

Products: Using CR 8.5 within Visual Studio.NET 2002 for a VB.NET windows application. SQL Server 2000 is the database.
Attempting: Want to use the "push" method to get data into my crystal report.

I've found a couple of tutorials to accomplish this such as

http://aspalliance.com/articleViewer.aspx?aId=265&pId=5

I have a working Crystal Report bound to a SQL Server stored procedure so I know the connection works and data can get to the report. According to the tutorials I need to create an XSD based off of my stored procedure which Crystal can use as my "field templates." Then, when that is done I can obtain a dataset through my data layer and bind it dynamically at run-time. I need to do this to cut down on the records sent across the network. This all sounds great.

I use VS to create said XSD file which it does.
I go to the Field Explorer and select Add/Remove database and expand the Project Data -> ADO.NET datasets nodes and find my new dataset. (The dataset is also found in other parts of the explorer)
Here's the rub. Everytime I expand my dataset in the Field Explorer is lists "...no items found..." In other words, no field names to drag and drop into my application.

I've replicated this error at home on my Visual Studio 2003.
I have made sure "Generate Dataset" is checked under the schema menu of the dataset.
I have checked over the XSD file and it does indeed have the field names I need.
I have restarted Visual Studio.
I have checked permissions on the SQL Server stored procedure.
I have tried both integrated security and setting explicitly providing it with the username password my application uses for its ODBC connect string.
I am also plum out of other ideas.
All the tutorials I see on this topic indicates this should be just a routine procedure and I can't find any mention of a bug of this nature on MSDN.

What am I missing besides my mind?

ZW

 

[susiesunshine]

To update everyone, it wasn't just a problem through Crystal. Through Excel, the tables were invisible. We ended up rebuilding the database. I believe the original database install was the problem. Thank you everyone for your comments!

 

[ZombyWoof]

Still working on this issue. Thought I'd give an update.

The problem occurs not only with CR 8.5 as previously reported but with CR.NET as well. (The one that comes with VS.NET.) I've also had this machine upgraded to VS.NET 2003.

However, I doubt anyone has been able to replicate this error becuase it works fine on the other two machines I have tried. The only difference between those machines and this one where the error occurs is the operating system. This machine, with the error, runs Windows 2000 and the other two machines Windows XP Pro.

Is it feasable that the operating system is responsible for the Server Exploer in CR.NET not operating correctly?

ZW