FiveTech Software tech support forums

... to generate temp files with unique names and check to see if they are already existing and if so then generate a new temp name. You can do this by appending a number to the end of the filename, then checking to see if it exists, and if so, then increment the number and try again. You should also ...

... class (valid only when used with RDD. New: Method SetDefault( cField, uDefaultValue ). Parameter can be an array also To be used only when appending a record. New: DATA bValid. Record is saved only when Evaluating bValid, with self as parameter returns .t. New: Method lValid(). Used to ...

... particulary in the HB_FReadLine() function to look up for LF only and the split process went through without problems. Right now the program is appending records. As of now, DBF file size is over 10GB and still going. I'll post when the program finishes. Thank you very much.

For adChar and adVarChar you need to specify the Size as the 4th param.
oParam := oCmd:CreateParameter( "gsid", adChar, adParamInput, nSize )

For adNumeric or adDecimal, you have set Precision and NumericScale properties of the Paramter object before appending.

... "CUST" ) -----> oRec := TDataRow():New( oRs) You are right. Also by an oversight there is a bug in datarow.prg. This affects appending new record in ADO. Please make this correction in datarow.prg and use. Line 355: Instead of ::AddNew() Substitute oRs:AddNew()

... -------------- Class TDataRow simplifies the scatter/gather process of the field values of a single record of a table for purposes of editing/appending. This class can read all or specified field values from a single row of DBF table,ADO RecordSet, TDatabase object or XBrowse and save the ...

... it . Thanks in advance ! Can be done, but a bit complex. Let us also keep in mind that this is not based on a phantom row concept but is based on appending a new physical record and later deleting it if not filled by the user. When the user tries to go past the last row, xbrowse evaluates oBrw:bPastEof. ...

... it . Thanks in advance ! Can be done, but a bit complex. Let us also keep in mind that this is not based on a phantom row concept but is based on appending a new physical record and later deleting it if not filled by the user. When the user tries to go past the last row, xbrowse evaluates oBrw:bPastEof. ...

Yes it is possible (ARRAY ! ) as : aIns(oBrw:aArraydata,nAt,xValue,.T.) oBrw:Refresh() With a Dbf it is more complicated , but appending a record and defining the apropriate indexfiles must be enough to insert the record at the desired place. If not , you can try next routine // Not used ...

Marco,

I will try, appending in 2 Stepps the text to the Memo 1/2 + 1/2
didtn't test this.

Just tested with the same result : the MEMO doesn't append the next 2. Text.

Best Regards
Uwe

Hi Reinaldo. I made this function, appending yours, but I receive some errors during compiling process. I'm using Xharbour commercial. I'm doing something wrong ? Thanks a lot. Massimo ************************************************************************** ...

... were created as not editable should now be editable based on the If statement and the nEditType code block. Here is the snipit of code .. again, appending a new record flagging the 'LockedDown' field does not change the nEditType block at runtime .. As you can see in the AddNewRecord function ...

... We need to ensure that (1) repeated append is prevented as long as there is an unfinished append and (2) when the cursor row moves away from the appending row while the append is unfinished, the append should be cancelled properly. Extreme care should be taken for bOnPostEdit. It is highly desirable ...

Colin, There are two reasons I would not do what you did. 1) After appending a record you really want to keep it locked until you are done with the save, otherwise it is possible for another user to write data to that record. 2) If you modify the source, ...

Hi James After further tests I found that the record did not lock when the save was after appending a new record. if lNewJob   oJb:append()   oJb:save()              ** in save method the .or.  was ...