Unidac 8 and added options for Interbase connection

[toneskok]

Hi,

I'm using Unidac components for a long time and I'm very happy. Yesterday I downloaded version 8. Database in use is Firebird 2.5 (and FB 3 but not yet tested). Compiling went ok but when I run application all memo fields from DB were strange. Text in memo fields was not displayed properly (like čćšđž characters). Standard varchars were ok. Grid displayed memo icon instead of text. Just to be clear all worked ok in version 7.3.
On UniConnection component for Interbase provider I saw new options like "EnableMemos". I checked that and things started to work.
It is not a problem to make changes for new version and make adjustments but that parameter is not documented anywhere. And to make 50+ users unhappy is bad.
So, please explain to me what that parameter is for (and some others that are added and not documented), how memo handling routines were changed and why "EnableMemos" is not checked by default for compatibility.

Thank you and best regards, Tone

[ViktorV]

Thank you for providing the information and contributing greatly to our product's development.
Yes, we've added the EnableMemos option. You can use it to enable creating TMemoField and TWideMemoField for BLOB fields of subtype 1:
https://devart.com/ibdac/docs/devart.ib ... ememos.htm
We'll add this information to the UniDAC docs.

[toneskok]

Hi,

to create them where?
Beside creating this also affects retrieving memo fields subtype 1 and presenting them to dbgrid without appropriate charset (database is UTF8).

[ViktorV]

This property is used to create fields in a recordset and describe params.
In previous versions of UniDAC, the property defaulted to True, and the user wasn't able to change its value. The new version of UniDAC allows the user to change the value of the property that now defaults to False. To revert the behavior, you only need to set the property to True.

[toneskok]

Hi,

the point is not changing property to true but to maintain backward compatibility. I know changing to true solves problem but if something is by default true from version 1 (I don't know when property was introduced) it should stay true. Or at least write to change log "possible complications" or warning that something was before true is not anymore or the other direction.
But it looks that only I have problems.

Regards, Tone

[ViktorV]

We've changed that behavior at the request of our users. Now the behavior is more correct, we had to change the default value. Thank you for your valuable feedback and interest in our products.