Adding a Memo Field Changes Data in Number Fields

[carla]

Hello,

I am using CR 8.5 to create a report. There are several number fields in the report which show the correct data until I add in a memo field. When I add in the memo field it changes all of the data in the number fields to something completely incorrect. When I remove the memo field and refresh the report, the correct data appears in the number fields again.

Does anyone have any idea why this might happen and what I can do to fix it? The database I am reporting off of is Oracle 8.

Any help is greatly appreciated!
Thanks in advance,
Carla

 

[FVTrainer]

When you say "add in a memo field," do you mean that you are simply using drag and drop to add the field from the field explorer? Or are you changing a view or stored procedure to include the memo field and then adding it to the report?

 

[carla]

Hello,

Thanks for responding. I am adding in the memo field by dragging and dropping from the field explorer.

Carla

 

[FVTrainer]

Well, my first thought was that you needed to verify the database, but I'm not sure that is the case. It sounds like a driver problem. If you're using an ODBC connection, try changing to the native Oracle driver, or, if using the Oracle driver, try changing to an ODBC connection. I wish I had more of an answer...

 

[synapsevampire]

What connectivity are you using?

If ODBC, make sure that you use the CR supplied ODBC driver, not Oracles.

Whatever connectivity you're using, try changing it, that's usually the problem with this sort of thing.

Also you might use real examples rather than "completely incorrect"

-k

 

[lbass]

This behavior can also result from using an equal join between two tables where there are null values in the second table. If you only place fields from the first table on the report, all desired records will display. If you then add a field from the second table, the equal join is "activated" so to speak, and records from table 1 that don't have a match in table 2 will disappear. This obviously can cause problems with calculations.

I'm guessing that the memo field is from a table not otherwise used in the report. If this is the case, the solution is to change the join from Table1 to Table2 to a left join.

-LB

 

[carla]

There is actually only one table in the report. Changing the driver to the Crystal ODBC driver did the trick. All of my numeric fields are now showing the correct data.

Thanks for your help!
Carla

 

[synapsevampire]

Nae worries, I explain to developers over and over to use the CR ODBC drivers and they rarely believe me until they get some odd behaviors like this.

-k