Lars Fosdal

Leading question - so.... what would you check next, Mike?

I see the same in the D12.3 source, but no errors show in the IDE. I copied the source to another unit and compiled it and it doesn't care about semi-colons for external function declarations - not even for those with the delayed keyword. Bug or feature? I don't know, but it certainly is not consistent with the rest of the language.

SQL has always been for the Enterprise tier and up. In 12.3, support for SQL Server 2022 has been added.

TBH, I prefer C# for Azure functions.

Personally, I'd favour work that improves debugging - both in 32- and 64-bit. That said, even an incomplete 64-bit IDE is a step forward, and I am excited to see what can be achieved with the new compiler as it matures.

Is there a limit on usage at that price? Can a DB there be accessed from multiple concurrent instances of your app?

Were the crashes related to missing components?

There is a road-poster. It says "You are here".

There are numerous posts on StackOverflow on this topic, most asking why it is not working as expected 😛 Would it be an alternative to open the excel file in excel and use COM to extract the data from Delphi code?

@A.M. Hoornweg Passing the exception type and callstack info from the server would be useful for making an educated handling in the client, but I don't see why raising an exception in the client would be helpful. The callstack from the server side exception won't be the same as the callstack from an exception raised in the client,. It all depends on the client-side context, of course, so sometimes an exception may be acceptable, but frankly; I prefer to not raise an exception if I can handle a problem flow in a better way.

It isn't worse than your response having result codes that indicate success + data, or failure + type of failure, and your client responding to these the way you want it to. F.x Client -> Server, send me all the details on <some reference> <- Server: dude, that was a bad reference - I almost crashed! Client: Well, server didn't like that, so I better tell the user that the server couldn't find his shit and that the request upset the server.

Why would one declare an empty record?

Firstly, you need to know the nature of the exception. Do you use EurekaLog or MadExcept? If not, you are blind to the actual cause of the exceptions. Do you know what your code is doing when it stops processing requests or why it stops? Once you know what goes wrong, add checks to avoid execution when you have invalid data. It may be useful to have a try/except block to set return values that indicate a failure, instead of exiting by exception, but it is rarely useful to have "catch all" blocks simply to silence exceptions. Secure each piece of code that runs in a thread and uses shared resources with try/finally so that any resource you allocate can be returned to the shared pool, and any locks you grab can be unlocked.

Wrappers for Java/C/C++/C# are not trivial, depending on the complexity of structures and formats. Python might be an alternative - have a look in https://en.delphipraxis.net/forum/39-python4delphi/

https://docwiki.embarcadero.com/RADStudio/Athens/en/Using_the_Google_Play_In-app_Billing_Service