Oliver Morsch

As already mentioned in your stack overflow link, you should use the the backend. In your case "1" do you hide the edit server side (Delphi code)? Then you can there also save it server side! Maybe you can also encrypt the value or build a hash code you check later on server side. I think there is no other solution...

How? -> save server side!

You cannot trust data that comes from the client. Why do you want to save user name client side? That should be done server side saved in UniMainModule after login, then user cannot access and manipulate...

https://stackoverflow.com/questions/72369349/google-chrome-101-on-android-shows-tab-key-on-soft-keyboard-instead-of-enter-for

Then try mobile demo and when this works you can look in browser developer tools which properties this edit control has.

Is it correctly shown on mobile demo?

Which device and keyboard do you use? Is the number keyboard correctly shown in mobile demo?

This is the sorting in Excel: You are sorting it as string and that is the correct order for a string. Either you name it "Code-01", "Code-02", ... or must sort by it an integer column or calculated integer value.

https://learn.microsoft.com/en-us/windows/win32/services/interactive-services

I find my solution easier

Why not just create Delphi classes TInvDetail = class public seqNo: Integer; productCode: string; description: string; qty: Integer; price: Double; end; TInvoice = class public invNo: string; invDate: TDateTime; customer: string; invAmt: Double; invDetails: TArray<TInvDetail>; end; And then use var Invoice: TInvoice; begin Invoice := TJson.JsonToObject<TInvoice>(...) ???

see https://docs.devart.com/sdac/faq.htm: Are the SDAC connection components thread-safe? Yes, SDAC is thread-safe but there is a restriction. But the same TCustomMSConnection object descendant cannot be used in several threads. So if you have a multithreaded application, you should have a TCustomMSConnection object descendant for each thread that uses SDAC

But there is no SessionManager.Sessions.Lock That is definitely needed.

I would call the function SendUniSessionsToLicenseAPI(SessionText.Text) AFTER the s.unlock. So the Sessionlist is only locked for a short time.

Increases the memory on creating Report or on showing the PDF?