FiveTech Support Forums

FiveWin / Harbour / xBase community
Board index FiveWin para Harbour/xHarbour Comportamiento raro en xbrowse
Posts: 1364
Joined: Wed Jun 21, 2006 12:39 AM
Comportamiento raro en xbrowse
Posted: Mon Nov 05, 2012 04:03 PM

Estoy pasando una aplicación que se encuentra compilada en xHarbour a Harbour. Uso MySql como motor. Normalmente uso Array para levantar los datos y mostrarlos en xBrowse. He adjuntado el fuente de la clase al proyecto pero me ocurre un error raro. Cuando utilizo el método ToExcel, el control trata de leer el recordset y por supuesto me genera un error, ya que el recordset lo cierro una vez obtenidos los datos. Pero lo más extraño es que si lo desmonto del proyecto funciona perfectamente. Esto no pasaba con xHarbour. Estoy bastante decepcionado con este pasaje a pesar de que harbour parece más robusto. Alguien sabe ??? Gracias ...

Saludos

Posts: 1364
Joined: Wed Jun 21, 2006 12:39 AM
Re: Comportamiento raro en xbrowse
Posted: Mon Nov 05, 2012 07:08 PM
Aquí la descripción del error

Code (fw): Select all Collapse
Application
===========
   Path and name: C:\sipep_sql\SIPEP.EXE (32 bits)
   Size: 2,752,512 bytes
   Compiler version: Harbour 3.1.0dev (Rev. 17222)
   FiveWin  Version: FWH 12.03
   Windows version: 5.1, Build 2600 Service Pack 2

   Time from start: 0 hours 0 mins 4 secs 
   Error occurred at: 06/11/2012, 16:07:35
   Error description: Error BASE/1004  Message not found: NIL:FIELDS
   Args:
     [   1] = U   

Stack Calls
===========
   Called from:  => __ERRRT_SBASE( 0 )
   Called from: ../../../tobject.prg => NIL:ERROR( 0 )
   Called from: ../../../tobject.prg => (b)HBOBJECT( 0 )
   Called from: ../../../tobject.prg => NIL:MSGNOTFOUND( 0 )
   Called from: ../../../tobject.prg => NIL:FIELDS( 0 )
   Called from: C:\sipep_sql\xbrowse.prg => TXBROWSE:TOEXCEL( 6880 )
   Called from:  => (b)EVAL( 126 )
   Called from: .\source\function\MSGRUN.PRG => (b)MSGRUN( 36 )
   Called from: .\source\classes\DIALOG.PRG => (b)TDIALOG( 87 )
   Called from: .\source\classes\DIALOG.PRG => TDIALOG:DISPLAY( 0 )
   Called from: .\source\classes\DIALOG.PRG => TDIALOG:HANDLEEVENT( 873 )
   Called from:  => DIALOGBOXINDIRECT( 0 )
   Called from: .\source\classes\DIALOG.PRG => TDIALOG:ACTIVATE( 270 )
   Called from: .\source\function\MSGRUN.PRG => MSGRUN( 42 )
   Called from: C:\sipep_sql\PADRON.PRG => (b)INICIA( 126 )
   Called from: .\source\classes\TRBTN.PRG => TRBTN:CLICK( 676 )
   Called from: .\source\classes\TRBTN.PRG => TRBTN:LBUTTONUP( 854 )
   Called from: .\source\classes\TRBTN.PRG => TRBTN:LBUTTONDOWN( 758 )
   Called from: .\source\classes\CONTROL.PRG => TCONTROL:HANDLEEVENT( 1687 )
   Called from: .\source\classes\TRBTN.PRG => TRBTN:HANDLEEVENT( 1520 )
   Called from: .\source\classes\WINDOW.PRG => _FWH( 3153 )
   Called from:  => WINRUN( 0 )
   Called from: .\source\classes\WINDOW.PRG => TMDIFRAME:ACTIVATE( 980 )
   Called from: C:\sipep_sql\Sipep.prg => EMPIEZA( 199 )
   Called from: C:\sipep_sql\Sipep.prg => MAIN( 14 )


Gracias
Posts: 10733
Joined: Sun Nov 19, 2006 05:22 AM
Re: Comportamiento raro en xbrowse
Posted: Tue Nov 06, 2012 02:18 AM

There should not be any difference between xHarbour and Harbour.
Your code must be closing the recordset object before closing the browse window.

Regards



G. N. Rao.

Hyderabad, India
Posts: 1364
Joined: Wed Jun 21, 2006 12:39 AM
Re: Comportamiento raro en xbrowse
Posted: Tue Nov 06, 2012 11:24 AM

Rao, thanks for the reply but I do not think I understood

I'm going on an application that is compiled in xHarbour to Harbour. Using MySQL as. Normally used to lift Array data and display it in xBrowse. I have attached the source of the class to the project but I can think of a weird error. When I use the method ToExcel, the control tries to read the recordset and of course fails me as I close the recordset data once obtained. But the strangest thing is that if you dismount the project works perfectly. This did not happen with xHarbour. I'm pretty disappointed with this passage although Harbour seems more robust. Anyone know??? Thanks ...

Continue the discussion