CSVExport: was Re: [fpc-pascal] DBF Field name length and fpdbfexport

2011-09-07 Thread Reinier Olislagers
On 6-9-2011 9:14, Reinier Olislagers wrote: On 6-9-2011 8:32, Michael Van Canneyt wrote: On Tue, 6 Sep 2011, Reinier Olislagers wrote: Also, creating a Lazarus XMLSDExport component, and possibly rewriting CSVexport to use sdfdata, so it needs less code (current code basically duplicates what

Re: [fpc-pascal] DBF Field name length and fpdbfexport

2011-09-06 Thread Michael Van Canneyt
On Tue, 6 Sep 2011, Reinier Olislagers wrote: On 5-9-2011 23:20, Michael Van Canneyt wrote: On Mon, 5 Sep 2011, Reinier Olislagers wrote: Turns out the dbf export code needs at least another patch. DBF export missed support for ftfloat and other field types. Issue + patch at

Re: [fpc-pascal] DBF Field name length and fpdbfexport

2011-09-06 Thread Reinier Olislagers
On 6-9-2011 8:32, Michael Van Canneyt wrote: On Tue, 6 Sep 2011, Reinier Olislagers wrote: Wasn't aware of your/maintainers' preferences regarding naming, so I'll keep that in mind. To be honest, just thought you guys were lazy old fashioned to use I J as loop counter variables ;) No,

Re: [fpc-pascal] DBF Field name length and fpdbfexport

2011-09-05 Thread Reinier Olislagers
On 2-9-2011 14:38, Reinier Olislagers wrote: I think I've also found the solution to http://bugs.freepascal.org/view.php?id=20069 (patch attached), so if somebody would be so kind to review apply them, I'd be very happy. Turns out the dbf export code needs at least another patch. DBF export

Re: [fpc-pascal] DBF Field name length and fpdbfexport

2011-09-05 Thread Michael Van Canneyt
On Mon, 5 Sep 2011, Reinier Olislagers wrote: On 2-9-2011 14:38, Reinier Olislagers wrote: I think I've also found the solution to http://bugs.freepascal.org/view.php?id=20069 (patch attached), so if somebody would be so kind to review apply them, I'd be very happy. Turns out the dbf

[fpc-pascal] DBF Field name length and fpdbfexport

2011-09-02 Thread Reinier Olislagers
Hi all, If I Googled correctly, the following field size limits are present for the various DBase formats: 3: DBase III: 10 characters 4: DBase IV: 10 characters 7: DBase VII: 32 characters 8: FoxPro: 10 characters 3,4: http://www.clicketyclick.dk/databases/xbase/format/dbf.html#DBF_STRUCT 7:

Re: [fpc-pascal] DBF Field name length and fpdbfexport

2011-09-02 Thread Reinier Olislagers
On 2-9-2011 13:23, michael.vancann...@wisa.be wrote: On Fri, 2 Sep 2011, Reinier Olislagers wrote: Hi all, snip long-winded post Presumably, yes. Michael. ;) Thanks, I'll give it a go and attach a patch to Mantis... Reinier ___ fpc-pascal

Re: [fpc-pascal] DBF Field name length and fpdbfexport

2011-09-02 Thread Reinier Olislagers
On 2-9-2011 13:23, michael.vancann...@wisa.be wrote: On Fri, 2 Sep 2011, Reinier Olislagers wrote: snip In packages\fcl-db\src\export\fpdbfexport.pp These tablelevels/formats are defined: TTableFormat = (tfDBaseIII,tfDBaseIV,tfDBaseVII,tfFoxPro); In function function

Re: [fpc-pascal] DBF Field name length and fpdbfexport

2011-09-02 Thread michael . vancanneyt
On Fri, 2 Sep 2011, Reinier Olislagers wrote: On 2-9-2011 13:23, michael.vancann...@wisa.be wrote: On Fri, 2 Sep 2011, Reinier Olislagers wrote: snip In packages\fcl-db\src\export\fpdbfexport.pp These tablelevels/formats are defined: TTableFormat =

Re: [fpc-pascal] DBF Field name length and fpdbfexport

2011-09-02 Thread Reinier Olislagers
On 2-9-2011 15:09, michael.vancann...@wisa.be wrote: On Fri, 2 Sep 2011, Reinier Olislagers wrote: On 2-9-2011 13:23, michael.vancann...@wisa.be wrote: On Fri, 2 Sep 2011, Reinier Olislagers wrote: I think I've also found the solution to http://bugs.freepascal.org/view.php?id=20069 (patch

Re: [fpc-pascal] DBF Field name length and fpdbfexport

2011-09-02 Thread waldo kitty
On 9/2/2011 06:00, Reinier Olislagers wrote: may only contain the letters ‘a’-‘z’ and ‘A’-‘Z’, digits ‘0’-‘9’, and the underscore ‘_’ character well, that's interesting... i was writing back to say that the above all appeared as garbage characters while i was reading the message... evidently