Hi Ken;

This s NOT a desirable option as the ThemeNNN contents will change over time (ie: EBF, MR, Release, etc). IN PB2019 R@ you can also customize themes by App. So when you deploy an App under a specific version & build in particular, the matching THEME folder and its contents should be packaged ONLY with the App' EXE and *not* in a generic and hard coded location (like you describe in your example).

Instead, "relative" pathing or better yet UNC support needs to be used to dynamically locate the corresponding Theme folder for each specific App. For example relative addresing: ".\Theme" - where this folder is *always* located as a sub-folder of the deployed EXE; contains the theme name sub-folders and also more importantly, the over-rides that are now possible in PB2019 R2. These will always be *unique* to a specific App instance and thus need to dynamically associated to the App EXE's deployment *location* (not hardwired).

Just my $0.02 ... Food for thought. ;-)

Regards ... Chris

Hi Armeen / Muhammad ;

Setting the default in the App Object to "Do Not Use Themes" is the best. Unless you do this, there is *no* way to turn off any active Theme as the ApplyTheme() command is lacking support for an OFF functionality. For example ApplyTheme ( "" ) does NOT work. This is an issue in PB2019 and again 2019 R2.

The only way around this lack of functionality that I found is to perform a Restart() command and let the App object's "Do Not Use Themes" setting take effect during the restart process.