Database Data Width Differences

[Mel_Smith_(Guest)]

Kathleen:____ In the conversion of my R&R DOS V6.0a reports to R&R for Windows Version 9.0, I have the following ^weird^ occurrence:____ I have a field in a database defined as Character with a width of 96 and ^decimals^ as 2 (i.e. C(9,2)). This results in an actual character field of *608* characters. This is enough to hold my (very wide) character field without resorting to ^Memo^ field definitions.____ The DOS version of R&R (v6.0a) understands this long character field and very properly and correctly prints and wraps this field on the report nicely. (It even says: Size in Data File: 608 when examining the field in the report designer.____ OTOH, RRW V9.0 only sees the width as 96 characters and misses the remaining data in the field (several hundred extra characters)____Question: Is there any way to force RRW v9.0 to acknowledge and read the extra hundreds of chars in this field ??____TIA,____-Mel Smith__

[kfleming]

I am surprised that you can even create such a field and that the DOS version allows you to see the full character width. I can think of no V9 setting that would change the behavior of the windows version in handling this field.____Kathleen__R&R Support

[Mel_Smith_(Guest)]

Kathleen:____ Yes, I^ve been using that technique for years (to get around the field width of 255 chars for xBase databases). And, indeed V6.0a was perfect in that regard.____ So, instead of this method I^m going to have to change all these (1-record) databases to text files and attach them to V9.0 reports as RI_MEMO files. My fear is that I have (coming up) conversion of reports with more than one text file to attach ... (but that^s in another post) ____Thank you for the help !____-Mel Smith__