FiveTech Support Forums

acuellar wrote:Amigos

No funciona el Save() cuando las tablas están relacionadas con INNER JOIN.

Code (fw): Select all Collapse

oPDET:=oServer:Query( "SELECT P.*,concat_ws('',TRIM(D.APEPAT),' ',TRIM(D.APEMAT),' ',TRIM(D.NOM1),' ',D.NOM2) AS APENOM FROM PLANIDET AS P INNER JOIN DATPER AS D ON D.IDEMPL=P.IDEMPL ORDER BY APENOM FOR UPDATE") 


   oCol:=oBrw:AddCol()
   oCol:bEditValue:= { || oPDET:IVAACTUAL }
   oCol:cHeader:= "RC-IVA"
   oCol:nWidth:=53
   oCol:nEditType:=EDIT_GET
   oCol:bOnPostEdit:={|o, v, n| (oPDET:IVAACTUAL:=v,oPDET:Save()) } //Esto no funciona. Cómo se hace?

 //Esto tampoco funciona
  oSQL:=oPDET:GetRowObj()
   DEFINE DIALOG oDlg3 RESOURCE "VARIABLES" TITLE 'Variables'; oDlg3:lHelpIcon:=.F.
     REDEFINE GET oSQL:DTRAB   ID 103 OF oDlg3 UPDATE PICTURE "99.9" 
     REDEFINE GET oSQL:HEXTR   ID 104 OF oDlg3 UPDATE PICTURE "999.9"
     REDEFINE GET oSQL:HRECN   ID 105 OF oDlg3 UPDATE PICTURE "999.9"

     REDEFINE BUTTON oBtn ID 120 OF oDlg3 ACTION ( oSQL:Save(),oSQL:Refresh(),oDlg3:End() )
     REDEFINE BUTTON oBtn ID 121 OF oDlg3 ACTION (oDlg3:End())

     ACTIVATE DIALOG oDlg3 CENTERED

Creo que voy a tener que usar UPDATE PLANIDET SET con el que permite grabar

Gracias por la ayuda

Saludos,

Adhemar

Efectivamente Adhemar, si usas Dolphin, no puedes usar Save cuando la consulta no es una tabla simple, debes hacerlo con UPDATE o creando una nueva Query que contenga una sola tabla con las condiciones que deseas.

cmsoft wrote:Efectivamente Adhemar, si usas Dolphin, no puedes usar Save cuando la consulta no es una tabla simple, debes hacerlo con UPDATE o creando una nueva Query que contenga una sola tabla con las condiciones que deseas.

I am able to comfortably edit all fields of customer table and states table inline and they are saved automatically.

One important condition: The SQL should contain primary keys of tables, whether we browse or not.

Maurizio wrote:Hello Rao

I am able to comfortably edit all fields of customer table and states table inline and they are saved automatically.

One important condition: The SQL should contain primary keys of tables, whether we browse or not.

Is it possible to create a primary key in the function FWAdoCreateTable( ) ?

it would be very nice .

Maurizio
http://www.nipeservice.com

Thank Rao for your explanation ,

I mean a case like this

 aDbf := {}
 AADD (aDbf, {"PROG",    "N",  5 , 0 })  
 AADD (aDbf, {"NAME",    "C", 30 , 0 })  
 FWAdoCreateTable( "test" , aDbf , m->oServer, .t. )

and create with FWAdoCreateTable() a primary key on the file PROG directly , now Is possible with FW_AdoCreateIndex() .

Thanks
Maurizio

We are going off-topic for this post. Better you create another thread for similar topics.

FWAdoCreateTable( "test", { { "PROG", "N", 5, 0 }, { "NAME", "C", 30, 0 } }, oCn )
inserts one auto-increment column ID as the first column and as primary key.
The resultant table will have 3 columns ID,PROG,NAME with ID as auto-increment as primary key.

FWAdoCreateTable( "test", { { "PROG", "+", 5, 0 }, { "NAME", "C", 30, 0 } }, oCn )
Treats the first column PROG as auto-increment primary key column.
The resultant table will have 2 columns PROG,NAME with PROG as auto-increment primary key

It is possible to define your own primary keys like in the 2nd case.
But going by "good practices", I suggest the first alternative of creating a primary key which is not relevant to the user and not maintained by programmer.

This is the function to create indexes.
FW_AdoCreateIndex( oCn, cTable, cIndexName, aIndexCols, lUnique )

Example: FW_AdoCreateIndex( oCn, "CUSTOMER", "CUSTOMER_NAME_IDX", { "FIRSTNAME", "LASTNAME" }, .t. )

But I advise you not to create any indexes. It is not necessary in most cases. We can discuss in greater detail in a separate thread if you like.

Thank Rao ,
I agree .

Maurizio