Just to be complete:

I had a small error in test2.zip.

Here's the corrected version (Thank you Chris !!)

Now I've made a second test example.

(Test2.zip)

I wanted to check what happens when in the "Switch Theme" button, I DON't use a relative path to the Theme folder.

1) The theme folder is now called "theme190" instead of "mythemes"

2) I do an applyTheme() without specifying any path at all

3) It still works!! even after changing the internal current directory.

I thought it would be because there might be something cached, but I checked on a clean VM and it still works.

(had to add the atl100.dll by the way)

So my conclusion is that you might be doing something similar as to what I did in the first sample app, with a relative path OR you were missing some DLL's OR you are changing in such a way that the Runtime Dll's are no longer found OR ... might there be something wrong with your custom JSON file?

Kind of a mystery, but at least you have a solution with Ken's reply and my samples I hope.

regards,

I have done a small application to illustrate what I meant with "changing the internal directory of windows".

See the attached Zip.

1) Rename the shared folder of your Appeon powerbuilder installation(s) to something else temporarily for this test.

2) unzip the attachment somewhere

3) run the genapp.exe (so not from the powerbuilder IDE)

4) click on "Switch Theme" repeatedly, it'll cycle through the four standard themes.

5) click on "Do something that changes windows' internal directory"

6) click on "switch theme" again. It has stopped working because the operation on any other directory like reading or writing files, Dirlist() etc. has changed the current directory and the relative path to the folder with themes no longer works.

7) click on "set the current directory back to what it was ....

8) click on "swith theme" it should work again.

(by the way, I've assumed you have a C: drive, for the DirList() command to work)

Hope it helps

regards

Hi,

(this is just a guess of what might be happening).

So you are NOT doing an install of the pb runtimes?

If not, then you'd have to make sure that you don't change the "internal active directory" of windows with you code.

What I mean to say is that if for example you read an INI file somewhere in a different folder or wrte a log file or have a dialog popping up in which you select files from a different folder, then your internal windows directory no longer points to where the executable of you application is and thus won't find the runtime files anymore.

If doing operations with files in other folders, always use ChangeDirectory(...) to go back to the directory of the application afterwards.

HTH