Hi

In IBO 4.8.7 when code tried to add more text then a field could hold
the extra text was cropped and processing continued

i.e. 'My test text' into a varChar(10) resulted in 'My test te'.

In 5.2.x this sort of thing results in an exception being raised. This
is great for spotting data sizing issues and numeric overflows and can
easily be resolved by increasing field size or truncating data in code
using Copy().

This does have a major downfall though, in 4.8.7, increasing the DB
field size was 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.

So my question is their a 'flag' in IBO that can be used to turn the old
functionality back on. We would like to use the new functionality for
testing but on release we would want the old functionality !

Cheers
Rob