Not seeing database values in the Database Expert

[Former Member]

Greetings,

When I create a new OLE DB (ADO) connection to a database, there are two tables.

When I add both tables to the report, and look at the linking tab, one of the boxes contains values, but the other box does not.

My DBA has given me every permission known to man on this database, but the data still fails to show it self.

In the Parameter Expert, I can see the table, but I can not expand it even though there is a Plus symbol next to it in the tree.

[former_member183750 · Accepted solution]

What version of Crystal Reports (See in the designer Help Bout)

What database?

If you try ODBC, can you see the fields?

- Ludek

Senior Support Engineer AGS Product Support, Global Support Center Canada

Follow us on Twitter

[Former Member · Accepted solution]

I am using crystal 2008.

The datavbase is MS SQL.

We tried ODBC as well, with the same results.

I can see and use all of the data fields in the field explorer, but when I try to use the Formula Workshop to Build and SQL expression, I can expand the list of fields.

Thanks,

[former_member292966 · Accepted solution]

Hi Wade,

What datatypes are your fields defined as?  Some data types can't be used for anything except displaying.  BLOBs are an example.

What version of SQL Server are you using and when you use ODBC or OLEDB, what version of the drivers are you using?  Perhaps your drivers are older and don't recognize the data types.

Thanks,

Brian

[Former Member · Accepted solution]

In crystal it says that the field type is Memo. and how that you mention it, that makes sense with some of the errors I've been getting.

I'll have to check on the drivers and sql version, but I'm pretty sure they are up to date.

Thanks for the help.

W

[former_member183750 · Accepted solution]

Get the install update to SP 6:

https://share.sap.com/a:328ro3/MyAttachments/9aa22691-9773-4d64-b904-62775b5fec33/

The see this:

For OLE DB then use:

MS SQL 2005 - OLE DB Provider

MS SQL 2008 - SQL Native 10

MS SQL 2012 - SQL Native 11

MS SQL 2013 - SQL Native 11

For ODBC then use:

MS SQL 2005 - SQL Native

MS SQL 2008 - SQL Native 10

MS SQL 2012 - SQL Native 11

MS SQL 2013 - SQL Native 11

- Ludek

[Former Member · Accepted solution]

Thanks for all the help. It turned out to be the data type.