>> IT WORKS! I definitively vote for documentation. Now, documentation is
>> where I can do something. I cannot add anything to the development of
>> TSQLQuery itself, so much is made more than clear. But, I am happy
>> that the component works the way I expected it to work.
>
>Glad to hear. But i
> would like to discuss (and hopefully learn) about other things I
> found.
It always amazes me how people can have huge problems with the most
simple things. It probably means that there has to be something wrong,
somewhere. (Documentation?) Are you familiar with datasets in Delp
Over the past few days I have tried creating and editing new records with
the TSQLQuery component. I succeeded, but with quite a workaround.
As stated in bug report 0016076 (not authored by me) TSQLQuery gives errors
if you try to create a new record and think TSQLQuery would all handle it.
The is
I am working on allowing multiple axes in TAChart (issue 0013832). I am
working with the idea to have multiple x and multiple y axes for line
series.
At this moment the axes do not have minimum and maximum values (I've
submitted issue 0015371). As far as I know, the minimum and maximum
values
