On 7-8-2011 18:28, Ludo Brands wrote:
>> FTestDataSet.FieldByName('ftVarBytes').AsString:=TestString;
>> FTestDataSet.FieldByName('ftVariant').AsString:=TestString;
>
> Same problem as before: TBufDataset doesn't support correctly ftVarBytes and
> ftVariant and doesn't raise an SErrFieldTypeNo
> > Same problem as before: TBufDataset doesn't support correctly
> > ftVarBytes and ftVariant and doesn't raise an
> > SErrFieldTypeNotSupported like TMemDataset is doing. Look at
> > TCustomBufDataset.GetFieldSize and you'll see that data length for
> > ftVarBytes and ftVariant is arbitrarely
On 7-8-2011 19:50, Ludo Brands wrote:
>>> Same problem as before: TBufDataset doesn't support correctly
>>> ftVarBytes and ftVariant and doesn't raise an
>>> SErrFieldTypeNotSupported like TMemDataset is doing. Look at
>>> TCustomBufDataset.GetFieldSize and you'll see that data length for
>>> f
On 7-8-2011 19:50, Ludo Brands wrote:
> TBufDataset doesn't support ftVarBytes and ftVariant. Variants are complex
> objects and aren't stored by just copying bytes. Don't use them with
> TBufDataset.
>
> Ludo
>
... cause they have some kind of structure that describes what kind of
data the varia
> > TBufDataset doesn't support ftVarBytes and ftVariant. Variants are
> > complex objects and aren't stored by just copying bytes. Don't use
> > them with TBufDataset.
> >
> > Ludo
> >
> ... cause they have some kind of structure that describes
> what kind of data the variable/field actually
> On 7-8-2011 19:50, Ludo Brands wrote:
> > TBufDataset doesn't support ftVarBytes and ftVariant. Variants are
> > complex objects and aren't stored by just copying bytes. Don't use
> > them with TBufDataset.
> >
> > Ludo
> >
> ... cause they have some kind of structure that describes
> what k
