Xailer & OZ Software

Unfortunatly somthing is wrong with the new version.
Recompiling all project files the app shows an error
message at a position running without errors till now.
See the picture
This is the code line 452
aAdr:=(::oMp3:Alias())->(MakeAdr())
Even though the DataSet ::oMP3 was opened already when
the form was initialized I inserted new opening lines
before this line
::oMp3:Open()
::oMp3:Goto(::oMp1:FA3)
aAdr:=(::oMp3:Alias())->(MakeAdr())
But the error occurs nevertheless.
Add to this the messagebox has some bugs too.
The "Detail" and the "Fehler" buttons end the app.
The right button has the wrong caption.
The error text looks like that
Xailer-Version: %1
Compiler: %2
C/C++-Compiler: %3

Information über die interne Fehlerbehandlung
Untersystemaufruf: %1
Systemcode: %2
Default-Status: %3

Arbeitsbereiche
Arbeitsbereichnr.: %1
Aliasname: %2
Aktueller Datensatz: %3

jüngste Dateien (b)XDBFDATASET:XDBFDATASET (75)
TDBFDATASET:GOTO (0)
KSTAMM:PRINTLABCLICK (451)
TBUTTON:ONCLICK (0)
TBUTTON:CLICK (102)
(b)XCONTROL:XCONTROL (141)
TBUTTON:COMMAND (0)
TFOLDERPAGE:WMCOMMAND (251)
KSTAMM:SHOWMODAL (0)
TTABELLE:EDIT (337)
TTABELLE:BRWDBLCLICK (365)
TDBBROWSE:ONDBLCLICK (0)
TDBBROWSE:WMLBUTTONDBLCLK (1987)
RUNFORM (0)
TAPPLICATION:RUN (191)
MAIN (16)
-----------------------------------< Keine >-----------------------------------
öffnet die ausgewählte Datei
öffnet die ausgewählte Datei
I hope this report can help to find the bugs soon.
Regards
Ingo
--

Attached files pre6b.zip (3.5 KB)Â

Ingo,
There was a problem with Xailer resource file. I attach with this message a
new one that I hope it fixes the wrong error display problem.
BTW, the runtime error reports that the file is not open when trying to use
the DataSet:Goto() method. Are you sure is open? Could we have a self
conteined example?
Regards,
"Ingo Junge-Herrmann" <[email=XPRO-0031BA74-01@10.0.0.11]XPRO-0031BA74-01@10.0.0.11[/email]> escribió en el mensaje
news:43c75b5f$[email=1@ozsrvnegro.ozlan.local...]1@ozsrvnegro.ozlan.local...[/email]
>
> Unfortunatly somthing is wrong with the new version.
> Recompiling all project files the app shows an error
> message at a position running without errors till now.
>
> See the picture
>
> This is the code line 452
>
> aAdr:=(::oMp3:Alias())->(MakeAdr())
>
> Even though the DataSet ::oMP3 was opened already when
> the form was initialized I inserted new opening lines
> before this line
>
> ::oMp3:Open()
> ::oMp3:Goto(::oMp1:FA3)
> aAdr:=(::oMp3:Alias())->(MakeAdr())
>
> But the error occurs nevertheless.
>
> Add to this the messagebox has some bugs too.
> The "Detail" and the "Fehler" buttons end the app.
> The right button has the wrong caption.
> The error text looks like that
>
> Xailer-Version: %1
> Compiler: %2
> C/C++-Compiler: %3
>
>
> Information über die interne Fehlerbehandlung
> Untersystemaufruf: %1
> Systemcode: %2
> Default-Status: %3
>
>
> Arbeitsbereiche
> Arbeitsbereichnr.: %1
> Aliasname: %2
> Aktueller Datensatz: %3
>
>
> jüngste Dateien (b)XDBFDATASET:XDBFDATASET (75)
> TDBFDATASET:GOTO (0)
> KSTAMM:PRINTLABCLICK (451)
> TBUTTON:ONCLICK (0)
> TBUTTON:CLICK (102)
> (b)XCONTROL:XCONTROL (141)
> TBUTTON:COMMAND (0)
> TFOLDERPAGE:WMCOMMAND (251)
> KSTAMM:SHOWMODAL (0)
> TTABELLE:EDIT (337)
> TTABELLE:BRWDBLCLICK (365)
> TDBBROWSE:ONDBLCLICK (0)
> TDBBROWSE:WMLBUTTONDBLCLK (1987)
> RUNFORM (0)
> TAPPLICATION:RUN (191)
> MAIN (16)
>
> -----------------------------------< Keine
> >-----------------------------------
>
> öffnet die ausgewählte Datei
> öffnet die ausgewählte Datei
>
>
> I hope this report can help to find the bugs soon.
>
> Regards
>
> Ingo


Attached files xailer.rar (24 KB)Â

Ingo,
There was a problem with Xailer resource file. I attach with this message a
new one that I hope it fixes the wrong error display problem.
BTW, the runtime error reports that the file is not open when trying to use
the DataSet:Goto() method. Are you sure is open? Could we have a self
conteined example?
Regards,
"Ingo Junge-Herrmann" <[email=XPRO-0031BA74-01@10.0.0.11]XPRO-0031BA74-01@10.0.0.11[/email]> escribió en el mensaje
news:43c75b5f$[email=1@ozsrvnegro.ozlan.local...]1@ozsrvnegro.ozlan.local...[/email]
>
> Unfortunatly somthing is wrong with the new version.
> Recompiling all project files the app shows an error
> message at a position running without errors till now.
>
> See the picture
>
> This is the code line 452
>
> aAdr:=(::oMp3:Alias())->(MakeAdr())
>
> Even though the DataSet ::oMP3 was opened already when
> the form was initialized I inserted new opening lines
> before this line
>
> ::oMp3:Open()
> ::oMp3:Goto(::oMp1:FA3)
> aAdr:=(::oMp3:Alias())->(MakeAdr())
>
> But the error occurs nevertheless.
>
> Add to this the messagebox has some bugs too.
> The "Detail" and the "Fehler" buttons end the app.
> The right button has the wrong caption.
> The error text looks like that
>
> Xailer-Version: %1
> Compiler: %2
> C/C++-Compiler: %3
>
>
> Information über die interne Fehlerbehandlung
> Untersystemaufruf: %1
> Systemcode: %2
> Default-Status: %3
>
>
> Arbeitsbereiche
> Arbeitsbereichnr.: %1
> Aliasname: %2
> Aktueller Datensatz: %3
>
>
> jüngste Dateien (b)XDBFDATASET:XDBFDATASET (75)
> TDBFDATASET:GOTO (0)
> KSTAMM:PRINTLABCLICK (451)
> TBUTTON:ONCLICK (0)
> TBUTTON:CLICK (102)
> (b)XCONTROL:XCONTROL (141)
> TBUTTON:COMMAND (0)
> TFOLDERPAGE:WMCOMMAND (251)
> KSTAMM:SHOWMODAL (0)
> TTABELLE:EDIT (337)
> TTABELLE:BRWDBLCLICK (365)
> TDBBROWSE:ONDBLCLICK (0)
> TDBBROWSE:WMLBUTTONDBLCLK (1987)
> RUNFORM (0)
> TAPPLICATION:RUN (191)
> MAIN (16)
>
> -----------------------------------< Keine
> >-----------------------------------
>
> öffnet die ausgewählte Datei
> öffnet die ausgewählte Datei
>
>
> I hope this report can help to find the bugs soon.
>
> Regards
>
> Ingo


Attached files xailer.rar (24 KB)Â

"Ignacio Ortiz de Zúñiga" <InvalidAccount@ozs.com> wrote:
>Ingo,
>
>There was a problem with Xailer resource file. I attach with this message
a
>new one that I hope it fixes the wrong error display problem.
>
>BTW, the runtime error reports that the file is not open when trying to
use
>the DataSet:Goto() method. Are you sure is open? Could we have a self
>conteined example?
>
>Regards,
>
Ignacio,
::oMp3:lOpen is .F.
I couldn't send you a sample, because it is a completly builded
app. I'm searching for the cause.
The next problem: I told you that if the TBrowse property
lTabStop is set to .F., the TBrowse doesn't accept any
mouseclicks. You or Jose answered it would be fixed but it
isn't so.
Regards
Ingo

"Ignacio Ortiz de Zúñiga" <InvalidAccount@ozs.com> wrote:
>Ingo,
>
>There was a problem with Xailer resource file. I attach with this message
a
>new one that I hope it fixes the wrong error display problem.
>
>BTW, the runtime error reports that the file is not open when trying to
use
>the DataSet:Goto() method. Are you sure is open? Could we have a self
>conteined example?
>
>Regards,
>
Ignacio,
::oMp3:lOpen is .F.
I couldn't send you a sample, because it is a completly builded
app. I'm searching for the cause.
The next problem: I told you that if the TBrowse property
lTabStop is set to .F., the TBrowse doesn't accept any
mouseclicks. You or Jose answered it would be fixed but it
isn't so.
Regards
Ingo

Ignacio,
the errormessagebox works now and I could find the cause
of the closed database:
WITH OBJECT KLabel():New(self)
IF lOk:=:ShowModal()==mrOk
lPrivat:=:oPrivat:lChecked
lPreview:=:oVorschau:lChecked
ENDIF
:End() //<---- there was ::End()
END
IF lOk
aAdr:=(::oMp3:Alias())->(MakeAdr())
.....
::End() was tolerated from pre6a but now it was related to the
DataSet and closed the database - Ooops .
But I have another problem not related to the newe version:
calling LogDebug() doesn't show the debugwindow. What to do?
Regards

Ignacio,
the errormessagebox works now and I could find the cause
of the closed database:
WITH OBJECT KLabel():New(self)
IF lOk:=:ShowModal()==mrOk
lPrivat:=:oPrivat:lChecked
lPreview:=:oVorschau:lChecked
ENDIF
:End() //<---- there was ::End()
END
IF lOk
aAdr:=(::oMp3:Alias())->(MakeAdr())
.....
::End() was tolerated from pre6a but now it was related to the
DataSet and closed the database - Ooops .
But I have another problem not related to the newe version:
calling LogDebug() doesn't show the debugwindow. What to do?
Regards

Ingo,
> The next problem: I told you that if the TBrowse property
> lTabStop is set to .F., the TBrowse doesn't accept any
> mouseclicks. You or Jose answered it would be fixed but it
> isn't so.
Exactly which mouse events are you trapping?
Regards,
"Ingo Junge-Herrmann" <[email=XPRO-0031BA74-01@10.0.0.11]XPRO-0031BA74-01@10.0.0.11[/email]> escribió en el mensaje
news:43c76a9b$[email=1@ozsrvnegro.ozlan.local...]1@ozsrvnegro.ozlan.local...[/email]
>
> "Ignacio Ortiz de Zúñiga" <InvalidAccount@ozs.com> wrote:
>>Ingo,
>>
>>There was a problem with Xailer resource file. I attach with this message
> a
>>new one that I hope it fixes the wrong error display problem.
>>
>>BTW, the runtime error reports that the file is not open when trying to
> use
>>the DataSet:Goto() method. Are you sure is open? Could we have a self
>>conteined example?
>>
>>Regards,
>>
>
> Ignacio,
>
> ::oMp3:lOpen is .F.
>
> I couldn't send you a sample, because it is a completly builded
> app. I'm searching for the cause.
>
> The next problem: I told you that if the TBrowse property
> lTabStop is set to .F., the TBrowse doesn't accept any
> mouseclicks. You or Jose answered it would be fixed but it
> isn't so.
>
> Regards
>
> Ingo

Ingo,
> The next problem: I told you that if the TBrowse property
> lTabStop is set to .F., the TBrowse doesn't accept any
> mouseclicks. You or Jose answered it would be fixed but it
> isn't so.
Exactly which mouse events are you trapping?
Regards,
"Ingo Junge-Herrmann" <[email=XPRO-0031BA74-01@10.0.0.11]XPRO-0031BA74-01@10.0.0.11[/email]> escribió en el mensaje
news:43c76a9b$[email=1@ozsrvnegro.ozlan.local...]1@ozsrvnegro.ozlan.local...[/email]
>
> "Ignacio Ortiz de Zúñiga" <InvalidAccount@ozs.com> wrote:
>>Ingo,
>>
>>There was a problem with Xailer resource file. I attach with this message
> a
>>new one that I hope it fixes the wrong error display problem.
>>
>>BTW, the runtime error reports that the file is not open when trying to
> use
>>the DataSet:Goto() method. Are you sure is open? Could we have a self
>>conteined example?
>>
>>Regards,
>>
>
> Ignacio,
>
> ::oMp3:lOpen is .F.
>
> I couldn't send you a sample, because it is a completly builded
> app. I'm searching for the cause.
>
> The next problem: I told you that if the TBrowse property
> lTabStop is set to .F., the TBrowse doesn't accept any
> mouseclicks. You or Jose answered it would be fixed but it
> isn't so.
>
> Regards
>
> Ingo

Ingo,
All the Datasets owned by any form are closed and destroyed when the form is
destroyed. In order to do some work after the ShowModal() method with the
DataSets you shoud use the property lHideOnClose to .T.
> calling LogDebug() doesn't show the debugwindow. What to do?
I'am been searching for your bugs this morning using intensively LogDebug()
with no problem at all. I really do not know what can be happen. Maybe the
window is out of bound. Could you try to put a break point in your app. to
see if then you can see the Debug window? Thanks.
Regards,
"Ingo Junge-Herrmann" <[email=XPRO-0031BA74-01@10.0.0.11]XPRO-0031BA74-01@10.0.0.11[/email]> escribió en el mensaje
news:43c7748b$[email=1@ozsrvnegro.ozlan.local...]1@ozsrvnegro.ozlan.local...[/email]
>
> Ignacio,
>
> the errormessagebox works now and I could find the cause
> of the closed database:
>
> WITH OBJECT KLabel():New(self)
> IF lOk:=:ShowModal()==mrOk
> lPrivat:=:oPrivat:lChecked
> lPreview:=:oVorschau:lChecked
> ENDIF
> :End() //<---- there was ::End()
> END
> IF lOk
> aAdr:=(::oMp3:Alias())->(MakeAdr())
> ....
>
> ::End() was tolerated from pre6a but now it was related to the
> DataSet and closed the database - Ooops .
>
> But I have another problem not related to the newe version:
>
> calling LogDebug() doesn't show the debugwindow. What to do?
>
> Regards
>
>

Ingo,
All the Datasets owned by any form are closed and destroyed when the form is
destroyed. In order to do some work after the ShowModal() method with the
DataSets you shoud use the property lHideOnClose to .T.
> calling LogDebug() doesn't show the debugwindow. What to do?
I'am been searching for your bugs this morning using intensively LogDebug()
with no problem at all. I really do not know what can be happen. Maybe the
window is out of bound. Could you try to put a break point in your app. to
see if then you can see the Debug window? Thanks.
Regards,
"Ingo Junge-Herrmann" <[email=XPRO-0031BA74-01@10.0.0.11]XPRO-0031BA74-01@10.0.0.11[/email]> escribió en el mensaje
news:43c7748b$[email=1@ozsrvnegro.ozlan.local...]1@ozsrvnegro.ozlan.local...[/email]
>
> Ignacio,
>
> the errormessagebox works now and I could find the cause
> of the closed database:
>
> WITH OBJECT KLabel():New(self)
> IF lOk:=:ShowModal()==mrOk
> lPrivat:=:oPrivat:lChecked
> lPreview:=:oVorschau:lChecked
> ENDIF
> :End() //<---- there was ::End()
> END
> IF lOk
> aAdr:=(::oMp3:Alias())->(MakeAdr())
> ....
>
> ::End() was tolerated from pre6a but now it was related to the
> DataSet and closed the database - Ooops .
>
> But I have another problem not related to the newe version:
>
> calling LogDebug() doesn't show the debugwindow. What to do?
>
> Regards
>
>

Ingo,
From Whatsnew.htm (Pre-release 4)
a.. Automatic free of TDataSets and TDataSource whein their forms are
closed:
This modification may break your code sin when the form is closed all its
DataControl are unlinked of its TDataSet and for that reason operations of
type Update() on the TDataSet will not perform any effect. To avoid this
problem just put the property lHideOnClose to true and do not forget to
perform a oMyForm:End() when you have finish the data saving
I can not understand why it did work with PR6a.
Regards,
"Ignacio Ortiz de Zúñiga" <InvalidAccount@ozs.com> escribió en el mensaje
news:43c779ae$[email=1@ozsrvnegro.ozlan.local...]1@ozsrvnegro.ozlan.local...[/email]
> Ingo,
>
> All the Datasets owned by any form are closed and destroyed when the form
> is destroyed. In order to do some work after the ShowModal() method with
> the DataSets you shoud use the property lHideOnClose to .T.
>
>> calling LogDebug() doesn't show the debugwindow. What to do?
>
> I'am been searching for your bugs this morning using intensively
> LogDebug() with no problem at all. I really do not know what can be
> happen. Maybe the window is out of bound. Could you try to put a break
> point in your app. to see if then you can see the Debug window? Thanks.
>
> Regards,
>
> "Ingo Junge-Herrmann" <[email=XPRO-0031BA74-01@10.0.0.11]XPRO-0031BA74-01@10.0.0.11[/email]> escribió en el mensaje
> news:43c7748b$[email=1@ozsrvnegro.ozlan.local...]1@ozsrvnegro.ozlan.local...[/email]
>>
>> Ignacio,
>>
>> the errormessagebox works now and I could find the cause
>> of the closed database:
>>
>> WITH OBJECT KLabel():New(self)
>> IF lOk:=:ShowModal()==mrOk
>> lPrivat:=:oPrivat:lChecked
>> lPreview:=:oVorschau:lChecked
>> ENDIF
>> :End() //<---- there was ::End()
>> END
>> IF lOk
>> aAdr:=(::oMp3:Alias())->(MakeAdr())
>> ....
>>
>> ::End() was tolerated from pre6a but now it was related to the
>> DataSet and closed the database - Ooops .
>>
>> But I have another problem not related to the newe version:
>>
>> calling LogDebug() doesn't show the debugwindow. What to do?
>>
>> Regards
>>
>>
>
>

Ingo,
From Whatsnew.htm (Pre-release 4)
a.. Automatic free of TDataSets and TDataSource whein their forms are
closed:
This modification may break your code sin when the form is closed all its
DataControl are unlinked of its TDataSet and for that reason operations of
type Update() on the TDataSet will not perform any effect. To avoid this
problem just put the property lHideOnClose to true and do not forget to
perform a oMyForm:End() when you have finish the data saving
I can not understand why it did work with PR6a.
Regards,
"Ignacio Ortiz de Zúñiga" <InvalidAccount@ozs.com> escribió en el mensaje
news:43c779ae$[email=1@ozsrvnegro.ozlan.local...]1@ozsrvnegro.ozlan.local...[/email]
> Ingo,
>
> All the Datasets owned by any form are closed and destroyed when the form
> is destroyed. In order to do some work after the ShowModal() method with
> the DataSets you shoud use the property lHideOnClose to .T.
>
>> calling LogDebug() doesn't show the debugwindow. What to do?
>
> I'am been searching for your bugs this morning using intensively
> LogDebug() with no problem at all. I really do not know what can be
> happen. Maybe the window is out of bound. Could you try to put a break
> point in your app. to see if then you can see the Debug window? Thanks.
>
> Regards,
>
> "Ingo Junge-Herrmann" <[email=XPRO-0031BA74-01@10.0.0.11]XPRO-0031BA74-01@10.0.0.11[/email]> escribió en el mensaje
> news:43c7748b$[email=1@ozsrvnegro.ozlan.local...]1@ozsrvnegro.ozlan.local...[/email]
>>
>> Ignacio,
>>
>> the errormessagebox works now and I could find the cause
>> of the closed database:
>>
>> WITH OBJECT KLabel():New(self)
>> IF lOk:=:ShowModal()==mrOk
>> lPrivat:=:oPrivat:lChecked
>> lPreview:=:oVorschau:lChecked
>> ENDIF
>> :End() //<---- there was ::End()
>> END
>> IF lOk
>> aAdr:=(::oMp3:Alias())->(MakeAdr())
>> ....
>>
>> ::End() was tolerated from pre6a but now it was related to the
>> DataSet and closed the database - Ooops .
>>
>> But I have another problem not related to the newe version:
>>
>> calling LogDebug() doesn't show the debugwindow. What to do?
>>
>> Regards
>>
>>
>
>

Ignacio,
left click to change the row for example.
Regards
"Ignacio Ortiz de Zúñiga" <InvalidAccount@ozs.com> wrote:
>Ingo,
>
>> The next problem: I told you that if the TBrowse property
>> lTabStop is set to .F., the TBrowse doesn't accept any
>> mouseclicks. You or Jose answered it would be fixed but it
>> isn't so.
>
>Exactly which mouse events are you trapping?
>
>Regards,
>
>"Ingo Junge-Herrmann" <[email=XPRO-0031BA74-01@10.0.0.11]XPRO-0031BA74-01@10.0.0.11[/email]> escribió en el mensaje
>news:43c76a9b$[email=1@ozsrvnegro.ozlan.local...]1@ozsrvnegro.ozlan.local...[/email]
>>
>> "Ignacio Ortiz de Zúñiga" <InvalidAccount@ozs.com> wrote:
>>>Ingo,
>>>
>>>There was a problem with Xailer resource file. I attach with this message
>> a
>>>new one that I hope it fixes the wrong error display problem.
>>>
>>>BTW, the runtime error reports that the file is not open when trying
to
>> use
>>>the DataSet:Goto() method. Are you sure is open? Could we have a self
>>>conteined example?
>>>
>>>Regards,
>>>
>>
>> Ignacio,
>>
>> ::oMp3:lOpen is .F.
>>
>> I couldn't send you a sample, because it is a completly builded
>> app. I'm searching for the cause.
>>
>> The next problem: I told you that if the TBrowse property
>> lTabStop is set to .F., the TBrowse doesn't accept any
>> mouseclicks. You or Jose answered it would be fixed but it
>> isn't so.
>>
>> Regards
>>
>> Ingo
>
>

Ignacio,
left click to change the row for example.
Regards
"Ignacio Ortiz de Zúñiga" <InvalidAccount@ozs.com> wrote:
>Ingo,
>
>> The next problem: I told you that if the TBrowse property
>> lTabStop is set to .F., the TBrowse doesn't accept any
>> mouseclicks. You or Jose answered it would be fixed but it
>> isn't so.
>
>Exactly which mouse events are you trapping?
>
>Regards,
>
>"Ingo Junge-Herrmann" <[email=XPRO-0031BA74-01@10.0.0.11]XPRO-0031BA74-01@10.0.0.11[/email]> escribió en el mensaje
>news:43c76a9b$[email=1@ozsrvnegro.ozlan.local...]1@ozsrvnegro.ozlan.local...[/email]
>>
>> "Ignacio Ortiz de Zúñiga" <InvalidAccount@ozs.com> wrote:
>>>Ingo,
>>>
>>>There was a problem with Xailer resource file. I attach with this message
>> a
>>>new one that I hope it fixes the wrong error display problem.
>>>
>>>BTW, the runtime error reports that the file is not open when trying
to
>> use
>>>the DataSet:Goto() method. Are you sure is open? Could we have a self
>>>conteined example?
>>>
>>>Regards,
>>>
>>
>> Ignacio,
>>
>> ::oMp3:lOpen is .F.
>>
>> I couldn't send you a sample, because it is a completly builded
>> app. I'm searching for the cause.
>>
>> The next problem: I told you that if the TBrowse property
>> lTabStop is set to .F., the TBrowse doesn't accept any
>> mouseclicks. You or Jose answered it would be fixed but it
>> isn't so.
>>
>> Regards
>>
>> Ingo
>
>

Ignacio,
sorry if you waste your time with me.
Setting a breakpoint results only the codeeditor is shown but not the debugwindow
where the parameters sending with
LogDebug()are normally shown.
Regards
"Ignacio Ortiz de Zúñiga" <InvalidAccount@ozs.com> wrote:
>Ingo,
>
>All the Datasets owned by any form are closed and destroyed when the form
is
>destroyed. In order to do some work after the ShowModal() method with the
>DataSets you shoud use the property lHideOnClose to .T.
>
>> calling LogDebug() doesn't show the debugwindow. What to do?
>
>I'am been searching for your bugs this morning using intensively LogDebug()
>with no problem at all. I really do not know what can be happen. Maybe the
>window is out of bound. Could you try to put a break point in your app.
to
>see if then you can see the Debug window? Thanks.
>
>Regards,
>
>"Ingo Junge-Herrmann" <[email=XPRO-0031BA74-01@10.0.0.11]XPRO-0031BA74-01@10.0.0.11[/email]> escribió en el mensaje
>news:43c7748b$[email=1@ozsrvnegro.ozlan.local...]1@ozsrvnegro.ozlan.local...[/email]
>>
>> Ignacio,
>>
>> the errormessagebox works now and I could find the cause
>> of the closed database:
>>
>> WITH OBJECT KLabel():New(self)
>> IF lOk:=:ShowModal()==mrOk
>> lPrivat:=:oPrivat:lChecked
>> lPreview:=:oVorschau:lChecked
>> ENDIF
>> :End() //<---- there was ::End()
>> END
>> IF lOk
>> aAdr:=(::oMp3:Alias())->(MakeAdr())
>> ....
>>
>> ::End() was tolerated from pre6a but now it was related to the
>> DataSet and closed the database - Ooops .
>>
>> But I have another problem not related to the newe version:
>>
>> calling LogDebug() doesn't show the debugwindow. What to do?
>>
>> Regards
>>
>>
>
>

Ignacio,
sorry if you waste your time with me.
Setting a breakpoint results only the codeeditor is shown but not the debugwindow
where the parameters sending with
LogDebug()are normally shown.
Regards
"Ignacio Ortiz de Zúñiga" <InvalidAccount@ozs.com> wrote:
>Ingo,
>
>All the Datasets owned by any form are closed and destroyed when the form
is
>destroyed. In order to do some work after the ShowModal() method with the
>DataSets you shoud use the property lHideOnClose to .T.
>
>> calling LogDebug() doesn't show the debugwindow. What to do?
>
>I'am been searching for your bugs this morning using intensively LogDebug()
>with no problem at all. I really do not know what can be happen. Maybe the
>window is out of bound. Could you try to put a break point in your app.
to
>see if then you can see the Debug window? Thanks.
>
>Regards,
>
>"Ingo Junge-Herrmann" <[email=XPRO-0031BA74-01@10.0.0.11]XPRO-0031BA74-01@10.0.0.11[/email]> escribió en el mensaje
>news:43c7748b$[email=1@ozsrvnegro.ozlan.local...]1@ozsrvnegro.ozlan.local...[/email]
>>
>> Ignacio,
>>
>> the errormessagebox works now and I could find the cause
>> of the closed database:
>>
>> WITH OBJECT KLabel():New(self)
>> IF lOk:=:ShowModal()==mrOk
>> lPrivat:=:oPrivat:lChecked
>> lPreview:=:oVorschau:lChecked
>> ENDIF
>> :End() //<---- there was ::End()
>> END
>> IF lOk
>> aAdr:=(::oMp3:Alias())->(MakeAdr())
>> ....
>>
>> ::End() was tolerated from pre6a but now it was related to the
>> DataSet and closed the database - Ooops .
>>
>> But I have another problem not related to the newe version:
>>
>> calling LogDebug() doesn't show the debugwindow. What to do?
>>
>> Regards
>>
>>
>
>

Ingo,
Then surely you debug window is simply out of bounds of your dekstop.
Please check that the checbox from the menu option: Tools - General
Options - IDE - Save on exit is unchecked.
Regards,
"Ingo Junge-Herrmann" <[email=XPRO-0031BA74-01@10.0.0.11]XPRO-0031BA74-01@10.0.0.11[/email]> escribió en el mensaje
news:43c78589$[email=1@ozsrvnegro.ozlan.local...]1@ozsrvnegro.ozlan.local...[/email]
>
> Ignacio,
>
> sorry if you waste your time with me.
>
> Setting a breakpoint results only the codeeditor is shown but not the
> debugwindow
> where the parameters sending with
> LogDebug()are normally shown.
>
> Regards
> "Ignacio Ortiz de Zúñiga" <InvalidAccount@ozs.com> wrote:
>>Ingo,
>>
>>All the Datasets owned by any form are closed and destroyed when the form
> is
>>destroyed. In order to do some work after the ShowModal() method with the
>
>>DataSets you shoud use the property lHideOnClose to .T.
>>
>>> calling LogDebug() doesn't show the debugwindow. What to do?
>>
>>I'am been searching for your bugs this morning using intensively
>>LogDebug()
>
>>with no problem at all. I really do not know what can be happen. Maybe the
>
>>window is out of bound. Could you try to put a break point in your app.
> to
>>see if then you can see the Debug window? Thanks.
>>
>>Regards,
>>
>>"Ingo Junge-Herrmann" <[email=XPRO-0031BA74-01@10.0.0.11]XPRO-0031BA74-01@10.0.0.11[/email]> escribió en el mensaje
>
>>news:43c7748b$[email=1@ozsrvnegro.ozlan.local...]1@ozsrvnegro.ozlan.local...[/email]
>>>
>>> Ignacio,
>>>
>>> the errormessagebox works now and I could find the cause
>>> of the closed database:
>>>
>>> WITH OBJECT KLabel():New(self)
>>> IF lOk:=:ShowModal()==mrOk
>>> lPrivat:=:oPrivat:lChecked
>>> lPreview:=:oVorschau:lChecked
>>> ENDIF
>>> :End() //<---- there was ::End()
>>> END
>>> IF lOk
>>> aAdr:=(::oMp3:Alias())->(MakeAdr())
>>> ....
>>>
>>> ::End() was tolerated from pre6a but now it was related to the
>>> DataSet and closed the database - Ooops .
>>>
>>> But I have another problem not related to the newe version:
>>>
>>> calling LogDebug() doesn't show the debugwindow. What to do?
>>>
>>> Regards
>>>
>>>
>>
>>
>

Ingo,
Then surely you debug window is simply out of bounds of your dekstop.
Please check that the checbox from the menu option: Tools - General
Options - IDE - Save on exit is unchecked.
Regards,
"Ingo Junge-Herrmann" <[email=XPRO-0031BA74-01@10.0.0.11]XPRO-0031BA74-01@10.0.0.11[/email]> escribió en el mensaje
news:43c78589$[email=1@ozsrvnegro.ozlan.local...]1@ozsrvnegro.ozlan.local...[/email]
>
> Ignacio,
>
> sorry if you waste your time with me.
>
> Setting a breakpoint results only the codeeditor is shown but not the
> debugwindow
> where the parameters sending with
> LogDebug()are normally shown.
>
> Regards
> "Ignacio Ortiz de Zúñiga" <InvalidAccount@ozs.com> wrote:
>>Ingo,
>>
>>All the Datasets owned by any form are closed and destroyed when the form
> is
>>destroyed. In order to do some work after the ShowModal() method with the
>
>>DataSets you shoud use the property lHideOnClose to .T.
>>
>>> calling LogDebug() doesn't show the debugwindow. What to do?
>>
>>I'am been searching for your bugs this morning using intensively
>>LogDebug()
>
>>with no problem at all. I really do not know what can be happen. Maybe the
>
>>window is out of bound. Could you try to put a break point in your app.
> to
>>see if then you can see the Debug window? Thanks.
>>
>>Regards,
>>
>>"Ingo Junge-Herrmann" <[email=XPRO-0031BA74-01@10.0.0.11]XPRO-0031BA74-01@10.0.0.11[/email]> escribió en el mensaje
>
>>news:43c7748b$[email=1@ozsrvnegro.ozlan.local...]1@ozsrvnegro.ozlan.local...[/email]
>>>
>>> Ignacio,
>>>
>>> the errormessagebox works now and I could find the cause
>>> of the closed database:
>>>
>>> WITH OBJECT KLabel():New(self)
>>> IF lOk:=:ShowModal()==mrOk
>>> lPrivat:=:oPrivat:lChecked
>>> lPreview:=:oVorschau:lChecked
>>> ENDIF
>>> :End() //<---- there was ::End()
>>> END
>>> IF lOk
>>> aAdr:=(::oMp3:Alias())->(MakeAdr())
>>> ....
>>>
>>> ::End() was tolerated from pre6a but now it was related to the
>>> DataSet and closed the database - Ooops .
>>>
>>> But I have another problem not related to the newe version:
>>>
>>> calling LogDebug() doesn't show the debugwindow. What to do?
>>>
>>> Regards
>>>
>>>
>>
>>
>

Ignacio,
now it's back!
Muchas gracias
Ingo
"Ignacio Ortiz de Zúñiga" <InvalidAccount@ozs.com> wrote:
>Ingo,
>
>Then surely you debug window is simply out of bounds of your dekstop.
>
>Please check that the checbox from the menu option: Tools - General
>Options - IDE - Save on exit is unchecked.
>
>Regards,
>

Ignacio,
now it's back!
Muchas gracias
Ingo
"Ignacio Ortiz de Zúñiga" <InvalidAccount@ozs.com> wrote:
>Ingo,
>
>Then surely you debug window is simply out of bounds of your dekstop.
>
>Please check that the checbox from the menu option: Tools - General
>Options - IDE - Save on exit is unchecked.
>
>Regards,
>

Ingo,
Sorry. You are completely right. I did not understand your problem from the
beginning.
I attach with this message the module corrected. I apologize for any
inconvenience. Any feedback is welcome.
Regards,
"Ingo Junge-Herrmann" <[email=XPRO-0031BA74-01@10.0.0.11]XPRO-0031BA74-01@10.0.0.11[/email]> escribió en el mensaje
news:43c77c98$[email=1@ozsrvnegro.ozlan.local...]1@ozsrvnegro.ozlan.local...[/email]
>
> Ignacio,
>
> left click to change the row for example.
>
> Regards
>
> "Ignacio Ortiz de Zúñiga" <InvalidAccount@ozs.com> wrote:
>>Ingo,
>>
>>> The next problem: I told you that if the TBrowse property
>>> lTabStop is set to .F., the TBrowse doesn't accept any
>>> mouseclicks. You or Jose answered it would be fixed but it
>>> isn't so.
>>
>>Exactly which mouse events are you trapping?
>>
>>Regards,
>>
>>"Ingo Junge-Herrmann" <[email=XPRO-0031BA74-01@10.0.0.11]XPRO-0031BA74-01@10.0.0.11[/email]> escribió en el mensaje
>
>>news:43c76a9b$[email=1@ozsrvnegro.ozlan.local...]1@ozsrvnegro.ozlan.local...[/email]
>>>
>>> "Ignacio Ortiz de Zúñiga" <InvalidAccount@ozs.com> wrote:
>>>>Ingo,
>>>>
>>>>There was a problem with Xailer resource file. I attach with this
>>>>message
>>> a
>>>>new one that I hope it fixes the wrong error display problem.
>>>>
>>>>BTW, the runtime error reports that the file is not open when trying
> to
>>> use
>>>>the DataSet:Goto() method. Are you sure is open? Could we have a self
>>>>conteined example?
>>>>
>>>>Regards,
>>>>
>>>
>>> Ignacio,
>>>
>>> ::oMp3:lOpen is .F.
>>>
>>> I couldn't send you a sample, because it is a completly builded
>>> app. I'm searching for the cause.
>>>
>>> The next problem: I told you that if the TBrowse property
>>> lTabStop is set to .F., the TBrowse doesn't accept any
>>> mouseclicks. You or Jose answered it would be fixed but it
>>> isn't so.
>>>
>>> Regards
>>>
>>> Ingo
>>
>>
>


Attached files Browse.rar (17.9 KB)Â

Ingo,
Sorry. You are completely right. I did not understand your problem from the
beginning.
I attach with this message the module corrected. I apologize for any
inconvenience. Any feedback is welcome.
Regards,
"Ingo Junge-Herrmann" <[email=XPRO-0031BA74-01@10.0.0.11]XPRO-0031BA74-01@10.0.0.11[/email]> escribió en el mensaje
news:43c77c98$[email=1@ozsrvnegro.ozlan.local...]1@ozsrvnegro.ozlan.local...[/email]
>
> Ignacio,
>
> left click to change the row for example.
>
> Regards
>
> "Ignacio Ortiz de Zúñiga" <InvalidAccount@ozs.com> wrote:
>>Ingo,
>>
>>> The next problem: I told you that if the TBrowse property
>>> lTabStop is set to .F., the TBrowse doesn't accept any
>>> mouseclicks. You or Jose answered it would be fixed but it
>>> isn't so.
>>
>>Exactly which mouse events are you trapping?
>>
>>Regards,
>>
>>"Ingo Junge-Herrmann" <[email=XPRO-0031BA74-01@10.0.0.11]XPRO-0031BA74-01@10.0.0.11[/email]> escribió en el mensaje
>
>>news:43c76a9b$[email=1@ozsrvnegro.ozlan.local...]1@ozsrvnegro.ozlan.local...[/email]
>>>
>>> "Ignacio Ortiz de Zúñiga" <InvalidAccount@ozs.com> wrote:
>>>>Ingo,
>>>>
>>>>There was a problem with Xailer resource file. I attach with this
>>>>message
>>> a
>>>>new one that I hope it fixes the wrong error display problem.
>>>>
>>>>BTW, the runtime error reports that the file is not open when trying
> to
>>> use
>>>>the DataSet:Goto() method. Are you sure is open? Could we have a self
>>>>conteined example?
>>>>
>>>>Regards,
>>>>
>>>
>>> Ignacio,
>>>
>>> ::oMp3:lOpen is .F.
>>>
>>> I couldn't send you a sample, because it is a completly builded
>>> app. I'm searching for the cause.
>>>
>>> The next problem: I told you that if the TBrowse property
>>> lTabStop is set to .F., the TBrowse doesn't accept any
>>> mouseclicks. You or Jose answered it would be fixed but it
>>> isn't so.
>>>
>>> Regards
>>>
>>> Ingo
>>
>>
>


Attached files Browse.rar (17.9 KB)Â

Ignacio,
here the sample with oBrw:lTabStop := .F.
Try to change the focused row (record) by mouse.
Do you see what I mean?
Regards
Ingo
--

Attached files tabla.zip (2.4 KB)Â

Ignacio,
here the sample with oBrw:lTabStop := .F.
Try to change the focused row (record) by mouse.
Do you see what I mean?
Regards
Ingo
--

Attached files tabla.zip (2.4 KB)Â