Lajos Juhász

If everything fails read the manual: https://docwiki.embarcadero.com/Libraries/Sydney/en/FireDAC.Comp.DataSet.TFDDataSet.CreateBlobStream

I get: 42 N N =DOLLAR(4967.32, 2) =DOLLAR(1515.61, 2) =DOLLAR(0, 2) =DOLLAR(58054.89, 2) =DOLLAR(4084.55, 2) I cannot spot the garbage.

Rebuilding the source without oppening it should be fine. The IDE should save correctly after you edit the files, didn't tried I stay on 100% (bought a 2k monitor in order not to have to change scalling.). If you're the only developer you can test on a single form, if after saving it running the application shows correctly you should be fine.

Debug your code and find out what is nil.

Batch files should stay it's still mentioned at MS documentation for example: https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/windows-commands The Command shell was the first shell built into Windows to automate routine tasks, like user account management or nightly backups, with batch (.bat) files.

Also everyone failed to notice a small detail: function AnsiReplaceStr(const AText, AFromText, AToText: string): string; It's a function not a procedure. You can try: cLast:=AnsiReplaceStr( cLast, ''', '''' );

David already said everything. With can cause that you access something that you doesn't think (new property, field, method). Calling FreeAndNil for a local object has no reason it's just a classic code smell. Your aim should be to write clean and maintanable code that cannot be achieved using with.

The same from me, please d.... c.d. th.. w....

There is no reason to verify the data after you generated the XML. It's always the best to verify in case the data is incorrect to change it and as a last step to generate the output.

I have up to date Windows 10 and have no issues using Delphi 11.2. (I don't have office 365.)

I did it in previous versions mostly XE5 and D2007 and always you have to change dfm then pas can be done by delphi.

In which version of Delphi? For me the IDE want to keep the class from the dfm. What's working for me is to select View as text to show the dfm (alt+f12) change the class for components and then switch back to pas and save the file then will Delphi ask to change the pas. A bit faster solution is to use refind with rules #migrate. Of couse you have to add dataset, datafield, valuechecked and valueunchecked properties.

Another options is to use FireDAC, Ole Automation or library to read xlsx files directly for example TMS Flexcel.

Why are you using WrieString / ReadString. It would be better: Myinifile.WriteInteger('LastDiskSkin', SkinFile, lst1.ItemIndex.ToString); lst1.ItemIndex :=Myinifile.ReadInteger('LastDiskSkin',SkinFile, -1); // or some default index.

I got one when commenting on this forum open an RSP ticket. (Edit. My current bug that I am unable to create a test case is when frame is marked as object instead of inline in the DFM. )

I got using Delphi 11.2 and build all: [dcc32 Fatal Error] F2084 Internal Error: AV7B7C4E22(7B730000)-R00000010-0

It's the name (and maybe even the username?), I guess HDD serial and some other information serials from the machine.

Unfortunately this is a known fact.

Another question is what is a Websocket server? Last time I checked websocket was a protocol.

Is it just me or D11.1 update 1 has a problem debugging a runtime package? I was changing/debugging the core runtime package for the application. The workflow was the folowing: 1.) compile the package, 2.) run the package inside a host application. 3.) Make change 4.) Restart the IDE. Without step 4 I would get instantly internal error.

That is the CPU view, the call stack is on the left side. It should contain something like this: :76f010cc win32u.NtUserWaitMessage + 0xc :00b4ab5e TApplication.Idle + $14E Vcl.Forms.TApplication.HandleMessage Vcl.Forms.TCustomForm.ShowModal mainrm.TForm1.Button1Click($3417030) Vcl.Controls.TControl.Click Vcl.StdCtrls.TCustomButton.Click Vcl.StdCtrls.TCustomButton.CNCommand(???) ...... Most probably the call stack will be empty, in which case open the threads windows with CTRL + ALT + T and select the first thread on the list.

It should be simply a build for every application. So far I have no choice as with every version some bugs are fixed and new are introduced that forces to move to even newer version and hope that (n+1)! will be stable for the applications I am working on. (For me it's easier as application on D11 are still in release candidates. New versions while the stable versions are compiled with XE5.)

It should be compatible, there are some corner cases where it is not. After update you should recompile everything (bpl+exe) just to be sure.

I didn't saw this one. On the other hand lately I mostly do debugging and doesn't create a lot of new forms.

It's strange it's closed as duplicate without the number of the other RSP. We don't know what is in the other RSP and its status.