... want to program in the way you program even in the next incarnation. I prefer programming for children. The day I program the way you program or treat people, I'd rather retire. Silvio, aprendí a programar en CLIPPER 5.3 y sigo usando el modus operandi de CLIPPER 5.3 hasta el día de hoy. Y no ...
Some notes that may help you. Please treat the syntax: ADD TO oBrw for creating columns as obsolete. This command was created many years back for compatibility with TCBrowse for easier migration from TCBrowse to TXBrowse. Same way, please do ...
Tim, You can read the reply's in the online software or .. - Your API reads it and you do what you want (make a treat) - They send for every reply a mail and you read the mail for processing - They send a SMS back, but that is for the customer to see - They send to a online platform ...
... "powershell.exe -windowstyle hidden -File procown.ps1" )RETURN NIL It creates a text file which is easy to treat to get the user name but it has 2 caveats: it opens a shell window that appears shortly and the function has to be executed as administrator dues ...
... i.e., the file name as text. By setting the datatype of the column to "F" ( oCol:cDataType := "F" ), we tell the xbrowse to treat the data as file name, read the contents of the file and display the contents of the file appropriately. Test: #include "fivewin.ch"function ...
... requires installation of ACE.OLEDB.12.0 64-bits version. - 2nd parameter lHeaders is optional and defaults to .t. This indicates whether to treat the first row as headers of the table. - If successful, returns Ado connection object. Returns nil on failure. FW_AdoTables( oCn ) lists all sheets ...
... MSSQL, Oracle only DateTime field type is avaiable for storing both simple dates and date-time values. Whether a particular field is to be treated as Date or DateTime field mostly depends on the usage. Accordingly FWH libraries treat fields containing pure Date values (without any time-part) ...
... MSSQL, Oracle only DateTime field type is avaiable for storing both simple dates and date-time values. Whether a particular field is to be treated as Date or DateTime field mostly depends on the usage. Accordingly FWH libraries treat fields containing pure Date values (without any time-part) ...
Do you want to treat the larger fields as character fields but not as memo fields? What is the size of your VarChar fields? The present limit is 100 chars. Is a limit of 255 chars enough for you? If I suggest modifications to the ...
... that need special save then I'm used to loading the example fields into variables: cName: = CU-> First CCognome: CU => Last and then to treat them in the dialog example @ 10.10 get aGet [1] var cName and then to save them Replace cu-> First with cName But James erased all
Hi Nages, So I dont see problem at all, right? I have plan to take look to it on the next days. Thanks I never faced any problem. We need to treat this field as ReadOnly field. XBrowse, TDataRow, TDataBase automatically treat the field as readonly and do not allow modification of this field. ...
... ) at the right time. We again request to specify the ArrayData in the XBROWSE command only but not use SetArray() directly. This enables how to treat the column definitions while preparing the xbrowse. Even this is not necessary oBrwO:aArrayData:= aOrigen Instead, please specify DATASOURCE aOrigen ...
... is no way you can return a TinyInt or Bit value from a Query, unless the field itself is TinyInt or Bit field. We need to instruct XBrowse to treat the numeric value as logical. This is how: #include "fivewin.ch"function Main() local oCn, oRs, oDlg, oBrw ...