Subject | What's the status of the xlSQL components? |
---|---|
Author | Svein Erling Tysvær |
Post date | 2008-01-25T15:30:36Z |
I tried to find these components on www.ibobjects.com to see if they were part of a bundle or sold separately, but failed. The only thing I can find is the XLSQL Reports version 1.3.2 RC1 Evaluate for IB Objects on yahoogroups. So what is the status of xlSQL for IBO?
I love these components, they make it a lot easier to transfer things from TIB_Grid to Excel (two components, four or five properties - one of them resembling a SQL select statement or script, an existing Excel file with named ranges, a TButton and two lines of code and that's it). Though there are still a few minor niggles remaining:
1) If a field contains one or more line shifts, the line in Excel often gets a lot higher (e.g. one line shift may make the record appear as if there were five line shifts.
2) If I name a range and want a border around this range, then the bottom border disappear when xlSQL fills this range.
3) The nag screen at startup is in general not readable (there are a few readable words, but mostly the screen is filled with accented characters - is the nag screen originally written in Cyrillic or some character set that is very different from English?)
4) I fail when I try to have visible lines on every two or three rows. This is likely due to me being too demanding or not understanding how to do this with xlSQL ;o)
Set
[Non-text portions of this message have been removed]
I love these components, they make it a lot easier to transfer things from TIB_Grid to Excel (two components, four or five properties - one of them resembling a SQL select statement or script, an existing Excel file with named ranges, a TButton and two lines of code and that's it). Though there are still a few minor niggles remaining:
1) If a field contains one or more line shifts, the line in Excel often gets a lot higher (e.g. one line shift may make the record appear as if there were five line shifts.
2) If I name a range and want a border around this range, then the bottom border disappear when xlSQL fills this range.
3) The nag screen at startup is in general not readable (there are a few readable words, but mostly the screen is filled with accented characters - is the nag screen originally written in Cyrillic or some character set that is very different from English?)
4) I fail when I try to have visible lines on every two or three rows. This is likely due to me being too demanding or not understanding how to do this with xlSQL ;o)
Set
[Non-text portions of this message have been removed]