Lars Fosdal

I ended up writing a small class around THTTPClient from System.Net.HttpClient. No need for the humongous REST.* classes.

Any company would add such a disclaimer when releasing unofficial "patches". It means: If it didn't work, don't blame us.

Alternatively, simply spawn a cmd.exe and execute net start / net stop commands. We've been doing that for years without any problems.

@chmichael - Have you been hacked?

Please, be civil.

uses WinApi.ShLwApi, ... type TCompareLogical = class(TComparer<String>) function Compare(const Left, Right: string): Integer; override; end; function TCompareLogical.Compare(const Left, Right: string): Integer; begin Result := WinApi.ShLwApi.StrCmpLogicalW(@Left[1], @Right[1]) end; procedure TForm1.Button1Click(Sender: TObject); var LArr: TArray<string>; begin LArr := ['1','1.1','1.1.1','1.2.1', '1.1.1.1','1.1.1.2','1.1.1.3','1.1.1.4','1.1.1.5','1.1.1.6','1.1.1.7','1.1.2' ,'1.1.2.1','1.1.2.2','1.1.3','1.1.3.1','1.1.4','1.1.4.1','1.1.4.2','1.1.5','1.1.5.1','1.1.6','1.1.6.1' ,'1.1.6.2 ','1.2','1.2.1.1','1.2.1.10','1.2.1.11','1.2.1.2','1.2.1.3','1.2.1.4','1.2.1.5' ,'1.2.1.6','1.2.1.7','1.2.1.8','1.2.1.9' ]; var Comp := TCompareLogical.Create; TArray.Sort<string>(LArr, Comp); Memo1.Lines.AddStrings(LArr); Thanks, @Stefan Glienke, I didn't know about that function. I also did not know about HIERARCHYID in SQL, so thank you for that one, @mofareh ORDER BY Cast ('/' + acc_numb + '/' AS HIERARCHYID)

Well, I am not that consequent, so I'll make do, doing it manually. It did take me 30+ years to develop this style for readability, though. One of the benefits of breaking before then, is that it becomes easy to comment out parts of the if condition. One of the benefits of the hanging indent on single line statements, is that it is easy to spot where the full statement ends. Readability is cruical. Maintainability improves with readability.

LOL, no 😄

/off-topic Preferences of code. I like begin/end for clarity. However, I also like unusual breaks before then and strange indentations of single statements. If only I could convince the formatter to do my bidding. procedure MyProcedure(a, b: Boolean); begin if a then begin if b then Beep else Beep end else begin if b // Kommentar then Beep else Beep; end; end;

I think I was fooled by my own expectations with regards to the simplicity of OAuth2 and functional level of the TOAuth2Authenticator. The C# code example can be found here, but it uses another assembly from Thinktecture to do the http parts. https://github.com/LarsFosdal/csharp-ion-api-sdk/blob/master/DotNetBackendOAuth2/Program.cs I'll ponder a little, google some more, and see if I can't crack this nut.

I have instrumented the C# app with logging, so I see exactly what happens. The challenge is convincing the Delphi REST components to do the same thing.

There also is a confusing comment here https://docwiki.embarcadero.com/CodeExamples/Sydney/en/FireDAC.SQLite_Encryption_Sample

It is just weird with the message saying that the DB is NOT encrypted? Ref. https://docwiki.embarcadero.com/Libraries/Sydney/en/FireDAC.Phys.SQLite.TFDSQLiteSecurity.CheckEncryption

Are you sure there is no way to convince FD to use the appropriate encryption method?

Why can't it connect?

What if you in the app, first export to json with UniDAC, then close all Unidac DB conns, and then import with FireDAC?

It might be a bit banale, but what about a new version of the old app that exports to a json or xml file, and then the new app can import from that json or xml file?

Nice idea, though. File a suggestion at https://quality.embarcadero.com/secure/Dashboard.jspa

Please enter a report in https://quality.embarcadero.com/secure/Dashboard.jspa

$ is not mentioned on that page, and $$ did not help.

That is interesting. Although, at that point the creation has been completed.

Have a look at C:\Users\Public\Documents\Embarcadero\Studio\22.0\Samples\Object Pascal\Database\RESTDemo

Note that as an alternative to post-build events in the IDE, you can use a build server - such as Continua CI. We use that. It triggers after a commit to Git, increment versions, builds, runs unit tests, and translates, signs, package and copy the variants to their respective staging shares, and creates a zipped copy. Amazing time saver that ensure all builds are consistently handled.

The given example does not have any spaces in the references, so quotes won't help for those - otherwise I agree.

The cost of maintaining multiple versions is staggering. With limited resources, it makes sense to focus on subscription users. I don't like it either, and I really don't like how they gimp the community version, but yeah - they are not MS with deep pockets filled from other products.