Jiwa

I have a really weird problem.

I have a view in SQL. Been there for years.
A few years ago I wrote a report which reads the data from that view.
It is basically looking at IN_Main, and the view gets the custom field data so that each row is a single product, and the columns are each custom field. Not too complicated.

Today I got occasion to check the report because the client reported that the report is not displaying the custom fields data.

In Crystal, when doing a 'verify database', the columns are missing from the Database Expert, Links tab as if they are not in the view at all.
And when running the report within Jiwa, doing a SQL trace reveals that the columns are not even getting referred in the SELECT statement.
It is like Cystal can no longer see those columns.
I have done a grant_all_user_tables just to be sure permissions are OK. This is in version 7.0.157 but I don't think it's a Jiwa problem - I think it may be more Crystal related.

It's bizarre so the above may seem like waffling rubbish so if there is anything unclear I am happy to clarify!

Are you doing a "Set datasource location" before the "verify database"?

Hi Danny
The new customsettingvalues.contents has type varchar(max). Crystal 2013 doesn't like this type. I've experience this before. when I create a view for a specific custom field, I just return the Contents field and invoiceid, when I add this view to the crystal report, I can see the invoiceid field but no "Contents" field.

I normally do view to convert the contents to varchar(254). Then I can see the Contents field in the report.

Lenny

Lenny gets the prize. Thanks!

lennykp wrote:The new customsettingvalues.contents has type varchar(max). Crystal 2013 doesn't like this type.

Oh dear... DEV-3068 comes back to bite us again!

DEV-5894 created to look into this.