FiveTech Software tech support forums

Silvio,

Class TDataBase has a destructor method, so when the object gets out of scope then it gets called

change local oDbf into static oDbf (or keep it in an array) so the object is not destroyed

Gracias Joao Muy interesante , le hechare un vistazo tranquilamente. por cierto he descubierto las funciones de la lib y he conseguido compilar, pro si a alguien le interesa las libs a incluir son hbsqlit3.lib pero tambien sqlite3.lib el include #include "..\contrib\hbsqlit3\hbsqlit3.ch" l...

... versiones anteriores, esta característica solo estará disponible si oCol: lMultiRowEdit está establecido en .T. * TDataRow: - Modificado el método destructor para la compatibilidad con xHarbour para la deivación de clases en TDatarow. * edit.prg: Corregido error en el método VarPut() viewtopic.php?f=3&t=36364 ...

... rows. With a view to keep backward compatibility this feature is made available only if oCol:lMultiRowEdit is set to .t. * TDataRow: - Modified destructor method for compatibility with xHarbour for derivation of classes from TDatarow * edit.prg: Bug fix in method VarPut() http://forums.fivetechsupport.com/viewtopic.php?f=3&t=36364 ...

... in the window. If oWnd is nil, XBrowser is used. 99. Zap() Zaps() all records. Fails if dbf is opened as shared or readonly. 100. td_Destroy() DESTRUCTOR This method calls ::Close() method. This method should not be called directly in the application and it is called by (x)Harbour when all ...

James,

I do not understand well... if I use Tdatabase 17:06 or earlier, there is no destructor and there has never occurred an error...

Mr. Rao,

Unfortunately, I too have the same error as before, if I modify the Close method and keep the destructor...

... the Close() or End() method is called and this solves the problem. At least it appears to be in my testing. I shall be discussing in detail about DESTRUCTOR methods and how they work and what is the purpose and benefits of td_Destroy soon. For now, let me say that a DESTRUCTOR method is called ...

I tested the code posted by Mr Diego Decandia on Aug 25th and seen the problem. It is also true we do not see the problem if we remove the DESTRUCTOR method td_Destroy(). But removal of this method is not the right solution. This method did not create a new problem. In fact it brought to light ...

Antonio,

Done. No errors.

Antonio Linares wrote:ok, thanks, in Class TDataBase remove this line:

// DESTRUCTOR td_destroy()

Also comment out this code:
/*
PROCEDURE td_destroy() CLASS TDataBase

::End()

RETURN
*/

ok, thanks, in Class TDataBase remove this line:

// DESTRUCTOR td_destroy()

Also comment out this code:
/*
PROCEDURE td_destroy() CLASS TDataBase

::End()

RETURN
*/

with x++ I get >>>Error BASE/1003 Variabile inesistente: X Errore avvenuto il 01/09/17, alle 18:54:58 PC: 'DIEGO-HP', Operatore: DIEGO Tempo dallo start: 0 hours 0 mins 7 secs Chiamato da: C:\fwh\source\classes\database.prg => TDATABASE:__DESTRUCTOR( 1360 ) Chiamato da: => TDATABASE:C...

... it doesn't end the object and TD_Destroy does nothing. TD_Destroy is NOT being called in the object. The definition in the Class definition is: DESTRUCTOR td_destroy() So apparently it is being called outside the class somewhere. James

... oRec ) } ) for user edit instead of default edit procedure. - Enhancement: Method SqlQuery() uses VFPOLEDB is installed for DBFCDX. - Added DESTRUCTOR method. oDbf := nil closes table and connections. * MENUS - Fixed: increase font resources - Updated function GetnHeightItem(): value initial ...

... oRec ) } ) for user edit instead of default edit procedure. - Enhancement: Method SqlQuery() uses VFPOLEDB is installed for DBFCDX. - Added DESTRUCTOR method. oDbf := nil closes table and connections.