Xailer & OZ Software

Mahanimann

> Ok. Do not worry. Nothing happened.
That's good, but I'm still embarrassed

(that's good too)
Paal

Mahanimann

> Ok. Do not worry. Nothing happened.
That's good, but I'm still embarrassed

(that's good too)
Paal

Mahanimann

> I have a completely different experience with the Xailer sales person.
> Also I belief that such an accusation should not be placed on a public
> forum, it's seems quite unfair to me.
Yes, of course you are right. The way I wrote that stuff was rude and plain
dumb. It was ment to be ...

Mahanimann

> I have a completely different experience with the Xailer sales person.
> Also I belief that such an accusation should not be placed on a public
> forum, it's seems quite unfair to me.
Yes, of course you are right. The way I wrote that stuff was rude and plain
dumb. It was ment to be ...

Mahanimann

> BTW, I did not like at all your comment about hiding information, you are
> completely wrong. You better be more cautious next time if you do not
> mind, in case you want to continue with us.
OOOPS!
Yes, you are right! When I re-read what I wrote I see that it's as stupid
as like I'm a ...

Mahanimann

> BTW, I did not like at all your comment about hiding information, you are
> completely wrong. You better be more cautious next time if you do not
> mind, in case you want to continue with us.
OOOPS!
Yes, you are right! When I re-read what I wrote I see that it's as stupid
as like I'm a ...

Mahanimann

> Is correct. Please reread Xailer license.
Yes I found it there. But as most others I "never" read the usually very
boring license, so an activation counter is completely new to me. I can live
with it though, even if I think information like that is vital, important
and very much belongs in ...

Mahanimann

> Is correct. Please reread Xailer license.
Yes I found it there. But as most others I "never" read the usually very
boring license, so an activation counter is completely new to me. I can live
with it though, even if I think information like that is vital, important
and very much belongs in ...

Mahanimann

Ignacio,
The string length problem has disappeared in version 1.8!
After installing v1.8 I cleaned the project, commented out the "set the
value of cSelect by code and not in the
object inspector" and put the SQL statement back into the project
inspector, recompiled and everything worked as ...

Mahanimann

Ignacio,
The string length problem has disappeared in version 1.8!
After installing v1.8 I cleaned the project, commented out the "set the
value of cSelect by code and not in the
object inspector" and put the SQL statement back into the project
inspector, recompiled and everything worked as ...

Mahanimann

Here's a picture of the error.

Attached files

Mahanimann

Here's a picture of the error.

Attached files

Mahanimann

> Further information on this link: http://xailer.info/eng/?p=22
I did go there and found this text:
> We have decided to put the activation counter at zero for all Xailer
> clients, therefore, with the new system you may active again some new
> machines with your license, but this does not ...

Mahanimann

> Further information on this link: http://xailer.info/eng/?p=22
I did go there and found this text:
> We have decided to put the activation counter at zero for all Xailer
> clients, therefore, with the new system you may active again some new
> machines with your license, but this does not ...

Mahanimann

Sorry for not responding earlier, I've been out travelling.
> Please can you try to set the value of cSelect by code and not in the
> object inspector and tell us your results.
I added this to frm_Kunder.prg....
METHOD FormInitialize( oSender ) CLASS frm_Kunder
::oDataSet:cSelect := "SELECT ...

Mahanimann

Sorry for not responding earlier, I've been out travelling.
> Please can you try to set the value of cSelect by code and not in the
> object inspector and tell us your results.
I added this to frm_Kunder.prg....
METHOD FormInitialize( oSender ) CLASS frm_Kunder
::oDataSet:cSelect := "SELECT ...

Mahanimann

I get the following error when compiling with a TSQLQuery:cSelect which is
2360 characters long:
frm_Kunder.xfm (23) Error E0030 Syntax error: "parse error at 'OUTER'"
Line #23 is where the WITH oDataSet .... :cSelect is initiated in the .XFM
file.
The "'OUTER'" word changes when I change the ...

Mahanimann

I get the following error when compiling with a TSQLQuery:cSelect which is
2360 characters long:
frm_Kunder.xfm (23) Error E0030 Syntax error: "parse error at 'OUTER'"
Line #23 is where the WITH oDataSet .... :cSelect is initiated in the .XFM
file.
The "'OUTER'" word changes when I change the ...

Mahanimann

> 2) Is not a question of priority I am afraid, is a question of logical
> integrity. For example asume the following:
>
> aItems:= {"One", "Two", "Three"}; aItemsBound := { 1, 2, 3 }
>
> If the user inputs "Four" or whatever, then nIndex should be zero and
> ItemsBound is useless
Yes ...

Mahanimann

> 2) Is not a question of priority I am afraid, is a question of logical
> integrity. For example asume the following:
>
> aItems:= {"One", "Two", "Three"}; aItemsBound := { 1, 2, 3 }
>
> If the user inputs "Four" or whatever, then nIndex should be zero and
> ItemsBound is useless
Yes ...

Mahanimann

>> point is that when skipping down the browse (in VIEW-mode) using K_DOWN,
>> the browse dataset enters EDIT-mode automatically when reaching EOF().
>> Try it (in VIEW-mode, push K_DOWN when standing on the last row in the
>> browse), and watch what happens to the GET's and the TDBNavigator ...

Mahanimann

>> point is that when skipping down the browse (in VIEW-mode) using K_DOWN,
>> the browse dataset enters EDIT-mode automatically when reaching EOF().
>> Try it (in VIEW-mode, push K_DOWN when standing on the last row in the
>> browse), and watch what happens to the GET's and the TDBNavigator ...

Mahanimann

>> When utilizing the :nDataType=="dtBOUND" feature .AND. :nStyle ==
>> csDROPDOWN
>> the combobox buffer is updated with the field value (or the :aItemsBound
>> value, I don't know) rather than the value from :aItems.
> The field value. You MUST 'of course' use csDROPDOWNLIST in order to use ...

Mahanimann

>> When utilizing the :nDataType=="dtBOUND" feature .AND. :nStyle ==
>> csDROPDOWN
>> the combobox buffer is updated with the field value (or the :aItemsBound
>> value, I don't know) rather than the value from :aItems.
> The field value. You MUST 'of course' use csDROPDOWNLIST in order to use ...

Mahanimann

> You should CANCEL edit mode when you move the row number on the browse. In
> my opinion is better to complete disable the Browse when in Edit mode.
> That is what we do on sample DbfData1
I totally agree and do that in my app, but that was not the point. The
point is that when skipping down ...

Se encontraron 216 coincidencias

Nueva versi

Nueva versi

Nueva versi

Nueva versi

Nueva versi

Nueva versi

Nueva versi

Nueva versi

Character length limit on TSQLQuery:cSelect?

Character length limit on TSQLQuery:cSelect?

Character length limit on TSQLQuery:cSelect?

Character length limit on TSQLQuery:cSelect?

Nueva versi

Nueva versi

Character length limit on TSQLQuery:cSelect?

Character length limit on TSQLQuery:cSelect?

Character length limit on TSQLQuery:cSelect?

Character length limit on TSQLQuery:cSelect?

TDBComboBox (and then again a browse) error (example included)

TDBComboBox (and then again a browse) error (example included)

TDBComboBox (and then again a browse) error (example included)

TDBComboBox (and then again a browse) error (example included)

TDBComboBox (and then again a browse) error (example included)

TDBComboBox (and then again a browse) error (example included)

TDBComboBox (and then again a browse) error (example included)