1. Buck Woolley
  2. PowerBuilder
  3. Thursday, 25 April 2024 16:26 PM UTC

PB 2019 R2 Build 2353

Can theme folders be accessed on a terminal server folder or must the theme folders be on the users workstation.  For instance...  from a person connected to a client environment.


App path is not a problem; the problem is when the themes are not on the local machine, it 's not working.  PB is looking for themes to be on the local computer

ApplyTheme ("\\LAPTOP-5RNO5PJ5\c$\Program Files (x86)\Appeon\Shared\PowerBuilder\theme190\Flat Design Misa")

Something like this is returning null -- not even -1

Any thoughts on using themes on a server and not on the workstation???



Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Thursday, 25 April 2024 18:41 PM UTC
  2. PowerBuilder
  3. # 1

Hi Buck;

  FWIW: It's probably your implementation that is the problem. My STD Framework is configured for C/S, PowerClient and PowerServer "themed" Apps. They are configured and work anywhere as M-Code, P-Code or 32/64 bit compiled PB Apps are deployed (real, VM, RDP, etc) ...

  • Copy the Theme Folders from the PB IDE install location to your PB App's workspace main folder.
  • Set the Application Object Theme tab page location to the "relative" location.
  • Use the ApplyTheme command with only the theme name
    • ie: ApplyTheme ( as_theme_name )    // no path - just the primary name.

FYI: Have a look at the STD Framework's OrderEntry Demo App application. The structure of the workspace folder, the deployment folder and the Projects used to compile & deploy the App as either a C/S, PC and / or PS based application.



Regards .. Chris

There are no comments made yet.
  • Page :
  • 1

There are no replies made for this question yet.
However, you are not allowed to reply to this question.
We use cookies which are necessary for the proper functioning of our websites. We also use cookies to analyze our traffic, improve your experience and provide social media features. If you continue to use this site, you consent to our use of cookies.