Crystal Reports/MySQL Reporting Wrong Datatype thread766-1081074

[PCSAARON]

I still did not resolve: thread766-1081074

As soon as I created the report in Crystal Reports 8.5, this report showed a MySQL "text" field as a memo data type in CR 8.5. When I saved the report, went back in the next day to finish the report, I verified the database and it said it fixed the "ado". I didn't make any changes to the table, however it didn't like the original memo field on the report. It NOW changed this memo field to a String[230]. Which I have not made any changes to the MySQL table. So why is Crystal Reports recognizing this NOW as a String if it is a determined length instead of a memo field? Anyone have any new clues? Please read the above thread for other peoples posts and helpful insights. Thanks in advance.

Aaron

 

[PCSAARON]

Ok, I checked the data in the table, I was curious WHY it was choosing string[230] and not 255. The ONLY record in the table that had any data in it contained text of 230 characters! I decided to ADD 100 more characters in the field data and then re-designed a new report, and it now shows String[255] as the new data type in Crystal Reports. MySQL stills shows "text" as it's datatype. Anyone have any suggestions? Thanks.

Aaron

 

[PCSAARON]

I wanted to post what I found so far. I DELETED the table row, which had only one row of data in it, and recreated the field with NO data in it. Now it takes it as a memo field. I think this is a bug SOMEWHERE either in Crystal Reports or MySQL ODBC. I am still using the old connecter, because the new connector had issues when I tried to use it with CR. I haven't tried it recently. Does anyone have any light they can shed on WHY this is happening? This will hamper any future table changes once there is data in these memo fields... I have had it happen already! I don't want to keep adding new fields just to fix a memo field issue!
Thanks in advance.

Aaron

 

[synapsevampire]

I responded to your other post, I doubt that Crystal would bother to address this, MySQL isn't ready for primetime and is still littered with bugs.

WIth most databases, one states the size at design time, with the exception of certain data types, which Crystal is aware of, and will mark them appropriately as MEMO fields regardless of their length.

Be assured that the problem is within the MySQL side, and there are plenty more of them...

-k

-k