Lars Fosdal

COM objects will work in a sub-thread if they are created after calling WinAPI.ActiveX.CoInitialize(nil) and destroyed before calling WinAPI.ActiveX.CoUnintialize, in that thread.

@David Heffernan - I took the liberty of splitting this off into a new thread. I think @Marco Cantu and @David Millington should look closer at this.

What happened to that document? https://web.archive.org/web/20171221023547/http://qc.embarcadero.com/wc/qcmain.aspx?d=107411 Edit: I took the liberty of splitting David's answer into a new thread.

Different part - as in Outside the sand box - but it seems the file system is fully virtualized. A bit odd that you cannot specify %APPDATA% in the deployment system, since that actually is the appropriate path. Write under AppData Windows 10, version 1903 and later: New files and folders created under the following directories are redirected to a per-user, per-package private location: Local Local\Microsoft Roaming Roaming\Microsoft Roaming\Microsoft\Windows\Start Menu\Programs In response to a file open command, the OS will open the file from the per-user, per-package location first. If this location doesn't exist, the OS will attempt to open the file from the real AppData location. If the file is opened from the real AppData location, no virtualization for that file occurs. File deletes under AppData are allowed if user has permissions. Windows 10, version 1809 and earlier: Copy-on-written to a per-user, per-app location. AppData is typically C:\Users\user_name\AppData.

On the other hand, APPX apps are supposed to be sandboxed - hence moving a file to a different part of the system might not be a good idea? I could be wrong about this, though.

Which looks like a shared folder - unless that part on the end is a user specific key. If you install it with a different user - is a new folder C:\Program Files\WindowsApps\MYAPPNAME_1.0.0.0_x86__?????? created, or is the same folder used? Looking at http://docwiki.embarcadero.com/RADStudio/Sydney/en/Deployment_Manager, all the examples simply uses .\ - so perhaps that is sufficient.

If you name it .\YourAppFolder\ Where is that folder created in the current user's file system?

Where is that folder created? When it creates a folder named %APPDATA% - Where does it create it? C:\users\username\%APPDATA% ? C:\%APPDATA% ? Where is it created?

Is the DB supposed to specific for the current user, or do you want a single DB for all users on the machine?

Where does it create that folder?

Does %APPDATA%\YourAppName\ work? It resolves to C:\Users\<username>\AppData\Roaming Alternatively, %LOCALAPPDATA% C:\Users\<username>\AppData\Local

Not able to reproduce. Steps?

Look at the TPath type in System.IOUtils.- it is cross platform and has a number of methods for getting "special" folders. http://docwiki.embarcadero.com/Libraries/Sydney/en/System.IOUtils.TPath_Methods

@Clément I could reproduce it, added 4 png's of varying size, got AV at step 7. Same stack trace as yours. Also cannot exit the IDE without saving the VCL as the same AV happens and interrupts the exit - regardless of if the form is in text mode or not. Add a QP issue, please.

@PeterPanettone - If you add _XRio to the last three, you won't get any issues with Rio when 10.5 arrives.

https://larsfosdal.blog/2020/06/09/preview-any-text-file/

Why the component designer? I'd do it a bit simpler and design an About form and fetch as much as possible about the application at runtime - such as the icon from the resources, and title, version, etc from the version resource. The company and contact info could be static text, or you put it into properties on the form. The form could have a simple memo where you would put in any additional info you would want to show.

I guess those also could raise issues, but being from Norway, it is rare that we have data with AM/PM. Since Windows Server 2012, Windows have insisted on yy.mm.dd hh.nn.ss for the Norwegian locale, and that has caused issues with exchanging dates as string with an MSSQL database through FireDAC. The "quick fix" that has stuck with us so far - probably because it just worked - is to change the time separator to : (colon) leading to yy.mm.dd hh:nn:ss on the application server that communicates with the database. Wherever that format is massaged within the Delphi conversions, that just works. There is a lot of relatively old code in the layers between the input and the database, so one day we may take time to figure out a better solution.

We've found that date conversion problems often stem from Windows 10 using the same separator for time and date.

Did the inherited destructor remember to call inherited?

Should prolly do a status summary on the issues of this thread and start a new one, but don't have time right now.

You can write apps for Win 7 if you take care, but the Delphi IDE itself does NOT support Windows 7.

Undeclared types probably do not have RTTI because it kinda pointless to be looking up an unnamed type using RTTI, since you don't have a name to look up. Besides, if you were using unnamed types in a class in production code, I'd fire you from my team.

@Stefan Glienke I concur.

Check registry HKEY_CURRENT_USER\Software\Parnassus OU\Core Is the value of Path set to C:\Program Files (x86)\Common Files\ParnassusShared ? - if not, make it so. Copy the 20.0 DLLs there as per earlier posts.