Subject | RE: [IBO] Field overflow exception |
---|---|
Author | Svein Erling Tysvær |
Post date | 2013-10-09T07:43:46Z |
>This does have a major downfall though, in 4.8.7, increasing the DB field size wasIf you do
>automatically handled by both code and data aware controls, if you put Copy() into
>code to prevent exceptions you break the ability to extend storage size by simply
>modifying the database. Any field change then also requires coding changes.
IB_Cursor1.Fields[0].AsString:=COPY(Edit1.Text, 1, 10)
then yes, you have to modify your code when changing field length. However, if you do
IB_Cursor1.Fields[0].AsString:=COPY(Edit1.Text, 1, IB_Cursor1.Fields[0].SQLLen)
(or similar), then I would assume no code changes to be required when modifying the field length (though a program restart might be required).
HTH,
Set