... of the corresponding fields of the DBF. I actually don't know why when I delete one it assigns a number in position 32, where I added the "recno" field as it is done on yunus.prg If I add and delete, a number is not inserted So we arrived at this conclusion which seems to work AEval( ...
... 1624 ) Called from: TEST.PRG => TESTDEL( 131 ) Called from: TEST.PRG => MAIN( 26 ) TO save a xbrowse ( with array with 31 record + "recno()") I made Check if there are deleted records if ! Empty( oBrowse:aDeleted ) AEval( oBrowse:aDeleted, { ...
... re-save on archive There's probably something I don't understand I have two dbf Report.dbf (oDbf) Formati.dbf ( oDbfMod) have 30 fields +1 for recno() at first for editing I take a record on Report.dbf oRecord := oDbf:record() create am array from another archive aDataForm := oDbfMod:DbfToArray( ...
... saved I can append the data or edit the data and the last thing I do with dbfcdx is to move the record pointer after I write to the disk with GoTo Recno() ADO is a bit different with SQL .. Recordsets can be added to or edited one record at a time and when a committ is made all I do is issue oRs:Update(), ...
... or table is unlocked then just before this operations RDD writes all local modifications in table and index files. 2. DBSKIP(0) just like DBGOTO( RECNO() ) writes all local modifications (if any) and then discards local record buffer so record has to be read again when any field is accessed. 3. ...
... available under DOS version 3.3 and above. Under DOS 3.2 or less, COMMIT flushes Harbour buffers to DOS. In a network environment, issuing a GO TO RECNO() or a SKIP0 will flush Clipper’s database and index buffers, but only a COMMIT will flush the buffers and perform a solid-disk write. Thus to ...
Size < 1 Kb, 255-32 Records, 1 x FIELD RECNO() -> CHR(x) This is the code for 255-32 records function Chars33to255() local oXlsx local cFile := "chars33to255.xlsx" local n,na, c, cx ...
... does not use "accent" Sign ) 2. How large is the dbf? Number of records and number of fields? Size < 1 Kb, 255-32 Records, 1 x FIELD RECNO() -> CHR(x)
... is 100% fullprove ? Yes. Safe and 100% full-proof. You need to carefully study the functions used carefully to appreciate the logic. Will the recno's not change when deleting of adding items to the invoice that will be saved ? This is the basic behavior of DBFs. When records are deleted, recno()s ...
... Yunus and how to retrieve invoice items, update en save. These function are used, but i'm not that sure yet. These functions are based on a recno() that is added and depending on the delete status of a invoice item. Deleted items are NOT taken by the function and so only GOOD items will ...