Re: Speedtest CLIPPER vs. xHarbour - COMMIT
Posted:
Fri Apr 30, 2021 11:52 am
by karinha
Can someone explain this command to me? Thanks.
- Code: Select all Expand view
set( _SET_HARDCOMMIT, .F. )
Regards.
Re: Speedtest CLIPPER vs. xHarbour - COMMIT
Posted:
Fri Apr 30, 2021 1:20 pm
by karinha
Gracias Maestro. Viviendo y aprendiendo.
- Code: Select all Expand view
HB_LANGSELECT( 'PT' ) // Default language is now Portuguese
HB_SETCODEPAGE( "PT850" )
RDDSETDEFAULT("DBFCDX")
RDDREGISTER( "DBFCDX", 1 ) // RDT_FULL
SET AUTOPEN OFF
SET CENTURY ON
SET DATE BRITISH
SET TIME FORMAT TO "HH:MM:SS"
SET EPOCH TO YEAR( DATE() ) - 30
SET SOFTSEEK OFF
SET WRAP ON
SETCANCEL( .F. )
SET CONFIRM OFF
SET DELETED ON
SET _3DLOOK ON
SET UNIQUE OFF
SET ESCAPE OFF
SET EXACT ON
SET EXCLUSIVE OFF
SET MULTIPLE OFF
// SET( _SET_HARDCOMMIT, .F. )
SET HARDCOMMIT OFF // Asi, és mejor.
SET OPTIMIZE ON
Regards, saludos.
Re: Speedtest CLIPPER vs. xHarbour - COMMIT
Posted:
Fri Apr 30, 2021 2:45 pm
by Rick Lipkin
To All
I still contend that when when you finish adding or editing a record in a .dbf .. a simple Goto Recno() is just as good as dbCommit() .. because you are moving the record pointer which flushes the buffers ...
Rick Lipkin
Re: Speedtest CLIPPER vs. xHarbour - COMMIT
Posted:
Fri Apr 30, 2021 3:55 pm
by karinha
Rick Lipkin wrote:To All
I still contend that when when you finish adding or editing a record in a .dbf .. a simple Goto Recno() is just as good as dbCommit() .. because you are moving the record pointer which flushes the buffers ...
Rick Lipkin
Sorry. I do not agree.
https://vivaclipper.wordpress.com/2014/01/17/dbcommit/https://vivaclipper.wordpress.com/2014/03/15/hb_frecno/https://vivaclipper.wordpress.com/?s=RECNO%28%29dbCommit (), Forces Windows to record data in the field in case of a power failure, for example.
Regards, saludos.