Olli73

Therefore I have used MATCHING (EST_ID, ESTDTLDSC) (And maybe additional fields), because ID is created by DB after post. But maybe there is another solution using the id field...

Have you also provided values for "providerType", "isFolder", ...? See my JSON above.

I have no experience with Microsoft API, but that looks to me that you do not need to create a sharelink first, instead you can directly enter the file or folder as sourceUrl: { "post": { "body": { "contentType": "text", "content": "I attached a reference to a file on OneDrive." }, "attachments": [{ "@odata.type": "#microsoft.graph.referenceAttachment", "name": "Personal pictures", "sourceUrl": "https://contoso.com/personal/mario_contoso_net/Documents/Pics", "providerType": "oneDriveConsumer", "permission": "Edit", "isFolder": "True" } ] } }

And this was my fault: You had a "b.*", not an "a.*".

The modify SQL should look something like this: UPDATE OR INSERT INTO ESTDTL (EST_ID, CSC_ID, ESTDTLDSC, CSTPLS, GSTINC, GSTPCT, QTYCLC, QTY, CST, GST, SLE, VAL) VALUES (:NEW_EST_ID, :NEW_CSC_ID, :NEW_ESTDTLDSC, :NEW_CSTPLS, :NEW_GSTINC, :NEW_GSTPCT, :NEW_QTYCLC, :NEW_QTY, :NEW_CST, :NEW_GST, :NEW_SLE, :NEW_VAL) MATCHING (EST_ID, ESTDTLDSC) RETURNING ESTDTL_ID, ESTDTLMNTDTE

The database file is missing...

And ARequest := arInsert; ARequest is no var parameter, so changing should have no affect!?

And is this condition true on insert: if (ARequest = arUpdate) and (ASender.FieldByName('EstDtl_ID').IsNull) then Normally it should be insert and not update for new record and the estdtl_id is not in the query, so that should raise an ecxception!?

In the query I would include the b.ESTDTL_ID to have a unique ID for "ESTTDL table" and in the insert I would set b.est_id to a proper value. What is the content if this est_id field? Can it be null?

When I understood you right, you have problems with inserting new records !? How looks your "TFDUpdateSQL.InsertSQL" ?

At least createCompomponents should not be synchronized so that components gets created in thread context.

Do you want to print under Windows or mobile phone? Under Windows you can follow the approach from Vincent. A printer driver must be installed under windows for that. Under mobile phone you should connect via bluetooth to the printer, establish a communication channel and send data in the "printer language" to the printer.

ConvertThreadToFiberEx is a WinAPI function which exists since Windows Vista, so it cannot work under XP.

Isn't it so that the IdContext is freed on connection loss and so I have no reference anymore to my data on reconnect? Then he could save the data reference in a dictionary (do not forget to use a locking mechanism) with IP address or any Unique Client ID as key and restore the data reference on reconnect.

Therefore I asked if it is Samsung! Samsung can everything except software! 😚