FiveTech Software tech support forums

Hi, I have a table like: Name    Link    Input   Name1   Name5   1   Name2   Name1   1Name3   Name20  1Name4   Name10  1   Name5   Name6   2Name6   Name11  1Name7   Name2   2   Name8   Name20  1Name9   Name1   1Name10  Name5   3Name11  Name1   1 ...

... This is what would be more or less And then in my web application, just like this ... myparameter: = PValue (1) Please call like this: index.prg?name1=value1&name2=value2 your index.prg function Main()   local hPairs :=  AP_Args()     ? ValToChar( ...

... for many years. To be exact, from FWH 10.02 onwards. oDbf:MapCol( cFieldName, cUserFriendlyName ) or oDbf:MapCol( { { "fld1", "name1" }, .... { "fldN","nameN" } } ) Small Sample:   local oDbf   oDbf  := TDatabase():Open( nil, "STATES", ...

... DBF 1 ------------------------- STATIC FUNCTION SET_SCOPE(cMonth) // the selected service-DBF ( Jan - Dec ) LOCAL cNName := UPPER((CUSTOMER)->NAME1) + UPPER((CUSTOMER)->NAME) // the cusomer name from DBF 1 to filter DBF 2 DBSELECTAREA( cMonth ) // DBF 2 (cMonth)->( ORDSCOPE( 0, NIL ) ...

... DBF 1 ------------------------- STATIC FUNCTION SET_SCOPE(cMonth) // the selected service-DBF ( Jan - Dec ) LOCAL cNName := UPPER((CUSTOMER)->NAME1) + UPPER((CUSTOMER)->NAME) // the cusomer name from DBF 1 to filter DBF 2 DBSELECTAREA( cMonth ) // DBF 2 (cMonth)->( ORDSCOPE( 0, NIL ) ...

... ) is exactly meant for this purpose only. First create browse like this: @ r,c XBROWSE oBrw <clauses> ; COLUMNS ; "NR", "NAME1", "NAME", "SIGNAL", ; 1, 2, 3, 4 "M_TOUR", "M_ZEIT", "M_MERKER" , ; 5, 6, 7 "N_TOUR", ...

Cristobal, Yes I think a column-data replacement is the better solution I tested at startup moving columns ( works ) // "NR", "NAME1", "NAME", "SIGNAL", ; 1, 2, 3, 4 // "M_TOUR", "M_ZEIT", "M_MERKER" , ; 5, 6, 7 // "N_TOUR", ...

... aDatT[1] := TRIM(("KUNDE")->ANREDE) aDatT[2] := TRIM(("KUNDE")->NAME) + " " + TRIM(("KUNDE")->NAME1) aDatT[3] := ("KUNDE")->ANSCHRIFT aDatT[4] := TRIM(("KUNDE")->PLZ) + " " + TRIM(("KUNDE")->ORT) ...

Uwe, OK, I have found what is going on. These two lines are not equivalent: set relation to upper(name1) into "serv" ORDSETRELATION("serv", {|| cust->name1}, "Serv->name1") ORDSETRELATION() does add a scope, but SET RELATION does not. ...

... ) NET_USE ( c_Pfad + "KUNDE.dbf", "KUNDE", 3, .T. ) DBSELECTAREA("KUNDE") ORDCREATE( ,"KUNDE1","UPPER(NAME1 + NAME)", ; {|| UPPER(NAME1 + NAME) } , .F. ) NET_USE ( c_Pfad + cMonat + ".dbf", "VPOS12", 3, .T. ) ORDCREATE( ,"VPOS12", ...

... to do some calculations on button < SAVE > FUNCTION PAT_GET() aDatP[1] := ("KUNDE")->ANREDE aDatP[2] := ("KUNDE")->NAME1 aDatP[3] := ("KUNDE")->NAME aDatP[4] := ("KUNDE")->ANSCHRIFT aDatP[5] := ("KUNDE")->PLZ aDatP[6] := ("KUNDE")->ORT ...

James,

WITHOUT using Scope ( 2. screenshot ) shows better results.

Instad using SCOPE I can activate
( "KUNDE" )->( ORDSETRELATION( cMonat, { || UPPER(NAME1 + NAME) }, "UPPER(NAME1 + NAME)" ) )
as a test

regards
Uwe

... row of SERVICES shows 38 fields As well the FOLDER-page is updated // CUSTOMERS REDEFINE XBROWSE oBrw1 ID 110 OF oDlg1 AUTOSORT ; COLUMNS { "NAME1", "NAME", "PFLSTUFE", "MERKER", "VARIANTE" } ; ALIAS "KUNDE" SET ORDER TO TAG KUNDE1 ... ...

... "KUNDE" ) ( "KUNDE" )->(DBSETORDER( "KUNDE1" )) ( "KUNDE" )->( ORDSETRELATION( cMonat, { || UPPER(NAME1 + NAME) }, "UPPER(NAME1 + NAME)" ) ) ( "KUNDE" )->( DBGOTOP() ) After selecting a row in browser 2, the values are displayed ...

... "KUNDE" ) ( "KUNDE" )->(DBSETORDER( "KUNDE1" )) ( "KUNDE" )->( ORDSETRELATION( cMonat, { || UPPER(NAME1 + NAME) }, "UPPER(NAME1 + NAME)" ) ) ( "KUNDE" )->( DBGOTOP() ) Browser 2 ( month with relation on names ) DBSELECTAREA( ...