FiveTech Software tech support forums

Saved me a few keystrokes
I normally would type as (oDbf:cAlias)->(dbSeek(cSeek, nil, .t.))

If you use database objects then you can just do:

oCustomer:goBottom()

Jimmy, I'm not sure I understand what you want to do but here is an example of adding a new sale amount to a oCustomer object using a function. Note that a customer object exists until you end it. Function addSale( oCustomer, nNewSale )   oCustomer:TotalSales := oCustomer:TotalSales: ...

... do: oDBF:ID := cID oDBF:Name := cName However you should always use a meaningful name for the database object, so it should be something like: oCustomer:ID oCustomer:Name You should not use oDBF as an object name because all that tells you is that it is a database object, but not which database ...

... do: oDBF:ID := cID oDBF:Name := cName However you should always use a meaningful name for the database object, so it should be something like: oCustomer:ID oCustomer:Name You should not use oDBF as an object name because all that tells you is that it is a database object, but not which database ...

... in OOP, and the only variable type I normally use is LOCAL. I don't use the type "FIELD" since I only use database objects (e.g. oCustomer:name), and thus no variable type declaration is needed for field names. You can also eliminate PUBLICs using a database object. I think you ...

... OOP articles. http://gointellitech.com/program.html 1) I want to create a Database as oDbf and pass oDbf much like we do with Ado .. oRs Simple: oCustomers:= TCustomers():new() Requires that you build a TCustomers class first. You can pass the object. You can also have objects within objects. ...

... 10, 10 XBROWSE oBrw1 SIZE 850, 525 PIXEL OF oFld:aDialogs[ 1 ] ; COLSIZES 40, 110, 110, 200, 150, 70, 100, 100, 100, 80, 60, 120, 160 ; DATASOURCE oCustomer AUTOCOLS LINES NOBORDER FONT oFont2 ; BACKGROUND cBackImg STRETCH UPDATE :D // OK see image doesn't work :( // TILED 0 // STRETCH 1 // FILL ...

... 10, 10 XBROWSE oBrw1 SIZE 850, 525 PIXEL OF oFld:aDialogs[ 1 ] ; COLSIZES 40, 110, 110, 200, 150, 70, 100, 100, 100, 80, 60, 120, 160 ; DATASOURCE oCustomer AUTOCOLS LINES NOBORDER ; BACKGROUND cBackImg FILL :!: the var cBackImg is new defined on folderpage 2 oBrw1:SetBackGround( cBackImg, BCK_FILL ...

Marc, I just saw this old message: The variable oCustomers should be declared as LOCAL. Note that you can still pass oCustomers to a function if you wish. Why not public? Then the oCustomers is visible everywhere and we don't have to paste them by ...

... you are trying to do, but if you use database objects you don't need to use local variables for fields--that is built into the database object. oCustomer:Name Is actually a buffer that contains a copy of the data in the NAME field. Also you never need to use workareas or aliases with database ...

Hello, I noticed a problem saving values with xBrowse edit_get using Browser 1 oCustomer := TDatabase():Open( , c_Path + "Customer", "DBFCDX", .T. ) only field LAST is working with some extracode the same using Browser 2 USE customer NEW SHARED ...

... compiled with FWH 19.09 don*t save the data anymore on celledit Reverse compiled with FWH 19.06 it works again. as well I tested using DATASOURCE oCustomer and OBJECT oCustomer with no difference ----------------- oCustomer := TDatabase():Open( , "CUSTOMER", "DBFCDX", .T. ) ...

oUsers:Invoices mimics "SET RELATION TO ..."

You select a user and invoices automatically deliver his invoices

I presume "users" is really describing customers?

You can use objects to do this too:

oCustomer:Invoices()

I need to return from a function a codeBlock type {|| oCustomer:First } but I Know the oDbf ( tdatabase ) and I have an array where are the fields of this archive so I have : Function bCampo( aCampos, nFor,oDbf) return oDbf:fieldWBlock(aCampos[nFor] ...

... double codes or searching at the time of saving Function EditCustomer(....) IF ladd cCustCode := CreateCode( "CUSTOMERS" ) ELSE IF oCustomer:Lastrec()==0 RETURN NIL ENDIF oCustomer:Load() cTitle := "Modify Customer" ENDIF define dialog ... REDEFINE GET oGet[1] VAR oCustomer:custNo ...