| Subject | Length of string fields in a IBOQuery |
|---|---|
| Author | patrick_marten |
| Post date | 2011-07-12T09:31:41Z |
Hello,
I'm testing the latest releases of IBObjects right now, which support unicode.
To port my application I took the easiest way and replaced TStringField by TWideStringField in all *.dfm and *.pas files, which worked fine.
Today I noticed a difference, though. A difference regarding the size, compared to a field, which I add via a IBOQuery.
In the database one of the fields is defined as "varchar (30)". That was also the size with the older release of IBObjects. If I delete this field from the query and add it again with the current release (build 9), the field is being added with a size of 120. A "varchar (50)" with the size 200 etc.
Are the new values correct and caused by unicode support or so?
Does it mean, that I have to remove and add all string fields via a IBOQuery again, so the previous sizes are set to the new values?
Regards,
Patrick
I'm testing the latest releases of IBObjects right now, which support unicode.
To port my application I took the easiest way and replaced TStringField by TWideStringField in all *.dfm and *.pas files, which worked fine.
Today I noticed a difference, though. A difference regarding the size, compared to a field, which I add via a IBOQuery.
In the database one of the fields is defined as "varchar (30)". That was also the size with the older release of IBObjects. If I delete this field from the query and add it again with the current release (build 9), the field is being added with a size of 120. A "varchar (50)" with the size 200 etc.
Are the new values correct and caused by unicode support or so?
Does it mean, that I have to remove and add all string fields via a IBOQuery again, so the previous sizes are set to the new values?
Regards,
Patrick