FiveTech Software tech support forums

... have been made only with ADS, MySql and MS Access. No change code required. Except: 1) As with ADS in index expressions you have to evaluate vars before send it to adordd. 2) Deleted records are immediately removed from table and cant be recovered again. So code like: Delete record recnoBlankRec() ...

... did. We just convert an app with ADS to MySQL with the new adordd developed by us. Not one single line of code change besides INDEX ON where the vars must be evaluated before but just like ADS. Ill post a new version fully working and tested in the next days . Although there are still small issues ...

... We are almost finishing ADORDD, but there is a problem converting some filters from Clipper sinatx to ADO Filter command: The problem is with the vars (oData:Codigo, cName)...:   SET FILTER TO FIELD->NAME = cName  SET FILTER TO AUXILIAR->RELACION  == alltrim(  STR( ...

... Please explain. Also, SET FILTER does not suport values, i.e: Code: SET FILTER TO LUCAS->NAME == cName Thats what I was speaking about. All vars must be evaluated before sent to ado filter once they are out of scope there. In order to be 100 % compatible with standard syntax we must evaluate ...

... So we must enter each corresponding function into SET ADO or SET ADODBF. Also please note that as in other rdds such as ADS all functions and vars in indexes must be evaluated before sending it to the server as the funcs or vars do not exist there. For and while and all Index parameters should ...

... Upper(cCity)+"'" Then the string would be: Upper(FIELD->City) ='LONDON' The same will happen in index expressions with vars. Sorry there isnt any other way. For us no problem because the app worked already with ADS and it was already doing that. Nevertheless this should ...

A small extension : I added predefined logical vars. It belongs to sample 2 and 4 can be replaced with any others lVar := { { .F., .F., .T., .T., .F., .F. } } added a message wait on button-click deleted the alerts creating a PRG and EXE ( only ...

Mr. Rao, it works fine now. Just a symple REFRESH needed. I forgot using vars inside the testbutton. ( late at night, I lost my concentration ) The used vars : nBColorF1 := 12434811 nBColorB1 := 16777215 nBGradPos1 := 0.50 nBColorF2 := 255 nBColorB2 := 16777215 ...

... oObj:value1 )msgInfo( oObj:value2 )  3) If the calling program is in the same prg as the function you could use file-wide static vars I highly recommend number 2, the class method. James

... > 0 will replace a record. A selected replace-checkbox will auto-switch from .T. to .F. if nesessary, to avoid double selections. sample : date-vars selected : < empty date > date vars changed to DATE() will reset the checkbox < empty date > selected before to .F. sample : 2 copies ...

Maybe do You want to < RESET or REPLACE > defined vars of the new record ? A test, using different copy-options for the destination record of types < numeric, logic and date > : I added a new logic-field in DBF customer, to show how to receive ...

The only way I know to put a buttonbar on a dialog is with the ON INIT clause. You can solve your PRIVATE vars issue by creating a class and declaring all the vars as DATA. Then you can just pass the class object. The object will then be holding all the data. Think OOP. You ...

... Well, you can resort to what you have been doing and assign each field to memory variable. This does mean writing lots of code to load those vars then save them. This gets very tedious very quickly. Fortunately, there is a better solution, and that is to use a record class which copies the ...

... Well, you can resort to what you have been doing and assign each field to memory variable. This does mean writing lots of code to load those vars then save them. This gets very tedious very quickly. Fortunately, there is a better solution, and that is to use a record class which copies the ...

I am trying to understand your code. Are TComp, TDesc, etc database objects? If so you don't need to create memory vars, you can just use the database object fieldname, ie oCust:name.

And please use the code tags when posting code so it retains its format.