Debugging
in [Visual Objects]
|
From: Horst Wetzel on 27 Feb 2007 12:32 Hi folks I have a problem with the dbserver-class. In a normal Browser-Window, which worked til today, I now get the dbserver-errror-message "33:data type error". I don't know, what I shoud have changed in the dbserver-class. I have restored the old dbserver modul -same error appears. For that is not the first time, I handled with such strange behaviour I now decided to debug until I find the point of this error. I looked in the SDK to search for all error points - loaded all this code in my own dbgdbServer-class - but could not find the cause and the exact point of interest. But I found a lot of instructions of the kind #IFDEF __DEBUG__ DBFDebug("Entering "+__ENTITY__, ASString(nRecordNumber)) This seems to be some kind of debugging, which is controlled by the expression __DEBUG__ , but I can't activate __DEBUG__ , because an expression DEFINE __DEBUG__ gives me a Compiler-Error. What do I have to do to activate this kind of debug. There must be a sort of switch in CAVO, which I do not know and which of course is not documented in any way! Please give me a hint and I will be very glad. kindly Horst Wetzel Lensing & Brockhausen GmbH kompetent in allen Zollangelegenheiten Reeser Stra�e 239 - 46446 Emmerich am Rhein Fon. +49 (0)2822 98 21 15 - Fax +49 (0)2822 98 21 35 www.Lensing-Brockhausen.com HRB 3489, Amtsgericht Kleve Gesch�ftsf�hrerin: Anette Br�derle
From: G Schaller on 27 Feb 2007 15:47 Horst. That won't work unless you compile that aef youself with debug and then include that lib in place of the VO internal one. In fact I provide an optimised RDD lib exactly for this kind of thing - you can get in with your own debug code. However I don't think that is your issue here. Show us the full error message please, including the line stack. I suspect you have a row with some bad data in it that will not convert to the proper data type for the fieldspec on that column. It usually indicates a data corruption in the DBF itself and will be why the version doesn't matter. Geoff "Horst Wetzel" <Wetzel(a)lb-zoll.de> wrote in message news:es1q02$d87$03$1(a)news.t-online.com: > Hi folks > > I have a problem with the dbserver-class. In a normal Browser-Window, which > worked til today, I now get the dbserver-errror-message "33:data type > error". I don't know, what I shoud have changed in the dbserver-class. I > have restored the old dbserver modul -same error appears. > > For that is not the first time, I handled with such strange behaviour I now > decided to debug until I find the point of this error. > > I looked in the SDK to search for all error points - loaded all this code in > my own dbgdbServer-class - but could not find the cause and the exact point > of interest. > > But I found a lot of instructions of the kind > > #IFDEF __DEBUG__ > DBFDebug("Entering "+__ENTITY__, ASString(nRecordNumber)) > > This seems to be some kind of debugging, which is controlled by the > expression __DEBUG__ , but I can't activate __DEBUG__ , because an > expression DEFINE __DEBUG__ gives me a Compiler-Error. > > What do I have to do to activate this kind of debug. There must be a sort of > switch in CAVO, which I do not know and which of course is not documented in > any way! > > Please give me a hint and I will be very glad. > > kindly > > > > Horst Wetzel > > Lensing & Brockhausen GmbH > kompetent in allen Zollangelegenheiten > Reeser Stra�e 239 - 46446 Emmerich am Rhein > Fon. +49 (0)2822 98 21 15 - Fax +49 (0)2822 98 21 35 > www.Lensing-Brockhausen.com > > HRB 3489, Amtsgericht Kleve > Gesch�ftsf�hrerin: Anette Br�derle
From: Horst Wetzel on 28 Feb 2007 06:38 Hi Geoff Thanks for answering. I invested some time to change my application to be able debugging RDD Classes. This wasn't easy, because I had to detach all librarys to avoid this stupid messages of "Class XXXXX doubly defined" and I couldn't find this double defintions! Now it works - But I can't see any Output of Outputdebugstring in dbgView in spite of teh fact, that this instruction is executed! But then I found the error - it was the code listed here: METHOD notify(kNotify, kDescription) CLASS dlgEdifact * * Hier werden die Kopffelder bei jeder Satzbewegung wieder deaktiviert! * IF kNotify = NOTIFYRECORDCHANGE SELF:oDCNACHRICHT:disable() SELF:oDCTNACHRICHT:disable() SELF:oDCVERSION:disable() SELF:oDCSGEBENE:disable() SELF:oDCSGGRUPPE:disable() SELF:oDCSGSTATUS:disable() SELF:oDCSGVARIANTE:disable() >>> SELF:SGWIEDERHG:disable() SELF:oDCSORTIERUNG:disable() SELF:oDCSEGMENT:disable() SELF:oDCSEGNAME:disable() SELF:oDCSEGMENTNR:disable() SELF:odcSEGNAME:disable() SELF:odcVARIANTE:disable() SELF:odcWIEDERHOLG:disable() SELF:odcEBENE:disable() SELF:odcdbStatus:disable() ENDIF RETURN SUPER:Notify(kNotify, kDescription) I didn't write this three letters "oDC" and I didn't excpect, that this code is executable and leeds to a database-error "33:data type error". I have wasted hours and hours looking for any error in the dbServer-definition - Is it really impossible to give the programmer a hint, in which piece of code such an error has it's origin? -- mit freundlichen Gr��en Horst Wetzel "G Schaller" <geoff(a)soft_ware.com.au> schrieb im Newsbeitrag news:45e49901(a)dnews.tpgi.com.au... > Horst. > > That won't work unless you compile that aef youself with debug and then > include that lib in place of the VO internal one. In fact I provide an > optimised RDD lib exactly for this kind of thing - you can get in with > your own debug code. > > However I don't think that is your issue here. > > Show us the full error message please, including the line stack. I suspect > you have a row with some bad data in it that will not convert to the > proper data type for the fieldspec on that column. It usually indicates a > data corruption in the DBF itself and will be why the version doesn't > matter. > > Geoff > > > > "Horst Wetzel" <Wetzel(a)lb-zoll.de> wrote in message > news:es1q02$d87$03$1(a)news.t-online.com: > >> Hi folks >> >> I have a problem with the dbserver-class. In a normal Browser-Window, >> which >> worked til today, I now get the dbserver-errror-message "33:data type >> error". I don't know, what I shoud have changed in the dbserver-class. I >> have restored the old dbserver modul -same error appears. >> >> For that is not the first time, I handled with such strange behaviour I >> now >> decided to debug until I find the point of this error. >> >> I looked in the SDK to search for all error points - loaded all this code >> in >> my own dbgdbServer-class - but could not find the cause and the exact >> point >> of interest. >> >> But I found a lot of instructions of the kind >> >> #IFDEF __DEBUG__ >> DBFDebug("Entering "+__ENTITY__, ASString(nRecordNumber)) >> >> This seems to be some kind of debugging, which is controlled by the >> expression __DEBUG__ , but I can't activate __DEBUG__ , because an >> expression DEFINE __DEBUG__ gives me a Compiler-Error. >> >> What do I have to do to activate this kind of debug. There must be a sort >> of >> switch in CAVO, which I do not know and which of course is not documented >> in >> any way! >> >> Please give me a hint and I will be very glad. >> >> kindly >> >> >> >> Horst Wetzel >> >> Lensing & Brockhausen GmbH >> kompetent in allen Zollangelegenheiten >> Reeser Stra�e 239 - 46446 Emmerich am Rhein >> Fon. +49 (0)2822 98 21 15 - Fax +49 (0)2822 98 21 35 >> www.Lensing-Brockhausen.com >> >> HRB 3489, Amtsgericht Kleve >> Gesch�ftsf�hrerin: Anette Br�derle >
From: G Schaller on 28 Feb 2007 16:48 > wasted hours and hours looking for any error in the dbServer-definition - Is > it really impossible to give the programmer a hint, in which piece of code > such an error has it's origin? Of course not. All you have to do is convince Brian that Robert should do some work on this. Good luck <g>
|
Pages: 1 Prev: X-Debug : New free utility for VO Next: mySQL4VO DataServer |