On 9-8-2011 12:17, Ludo Brands wrote:
I created a patch for ftVariant, ftBytes and ftVarBytes support as well as a
check for supported types and attached it to the issue. Feel free to extend
your tests with it ;)
Thanks, I'll have a look.
Also a change in fpXMLXSDExport line 388:
The format was defined as string before.
That doesn't match my current version.
Maybe I already made the change:
I've changed ftVariant to base64 encoding (i.e. treat is as
binary) in commit 19:
Mmm... That's taking risks and requires quite some testing with the
different host
On 9-8-2011 12:17, Ludo Brands wrote:
I created a patch for ftVariant, ftBytes and ftVarBytes support as well as a
check for supported types and attached it to the issue. Feel free to extend
your tests with it ;)
Applied patch in fpc source, make clean, make all make install for FPC,
make for
Applied patch in fpc source, make clean, make all make
install for FPC, make for Lazarus, rescan fpc source
directory, recompile test project.
Still get access violations.
(ftVariant, ftVarbytes set to size 10, then assigning all
kinds of strings to it using .AsString)
Could you have
On 9-8-2011 16:42, Ludo Brands wrote:
Downloaded the code and it raises an SUnsupportedFieldType when
creating the ftAutoInc field. That is OK since I didn't include
ftAutoinc in the supported list for TBufDataset. If you are not
getting this error, then the patch and/or install didn't work.
On 8/9/2011 10:42, Ludo Brands wrote:
Exception: Access violation
Source unit:
Method name:
Line number: 574
00.003 TestXSDExport_Access_NoXSD_NoDecimal Error:
Line 547 is where FillTestData is called. Not very usefull.
line 547 or 574? the error report
