Chris,
We tried downloading and running the redistributable package containing the DirectX Runtime as you suggested with no luck. We tried installing another DirectX runtime that we found on the Microsoft website, but that did not work either.
The only way we have gotten this to work on the user's computer thus far is to install PowerBuilder 2017 on the computer. Her computer is running Window 10 btw. Once installed, we ran the application from the IDE and when we open the screen with the graph on it, PowerBuilder prompted us to install DirectX Runtime. This appeared to be installing the same DLLs as in the DirectX Runtime you pointed us to. Once completed and we restarted the application from the IDE, the graphs had the 3D look we're expecting. When we then ran the network version of the executable on this computer, the 3D graphs looked correct.
However, when we uninstalled PowerBuilder 2017 the graphs reverted back to the flat look, although the color settings from the application were being used. (?!) It seems like PowerBuilder is doing something in addition to installing the DirectX Runtime DLLs in order for the application to use the 3D features. Is there a registry entry or some other DLL specific to PowerBuilder that is being installed on the user's computer?
Installing PowerBuilder 2017 on the user's computers or on our servers is not a solution. If we can identify what PowerBuilder is doing in addition to installing the DirectX Runtime DLLs then we might be able to use that going forward.
Any help would be greatly appreciated.
I've setup a graph for users to view and it appears as shown below on my computer. However, when the users run the application and open this graph, they do not see the 'cool' 3D graphs - they appear, "flat" and ignore the color settings I have in the application. I checked on their computer and it appears they have DirectX turned on with DirectDraw, Direct3D and AGP Texture Accelerations all Enabled. This is happening on the laptops for our sales people and on the desktop of several users running the application off our network.
Do I need to install some additional PowerBuilder DLLs on the target computers? Is there a list somewhere of those DLLs required to make the 3D graphs work?
I currently have the following DLLs in the directory where the users are running the application:
I'm sure they're not all needed, but the application runs without errors so I haven't tried challenging any of the files on this list.
I work with OP, Jeff, above. We tried downloading and running the redistributable package containing the DirectX Runtime as you suggested with no luck. We tried installing another DirectX runtime that we found on the Microsoft website, but that did not work either.
The only way we have gotten this to work on the user's computer thus far is to install PowerBuilder 2017 on the computer. Her computer is running Window 10 btw. Once installed, we ran the application from the IDE and when we open the screen with the graph on it, PowerBuilder prompted us to install DirectX Runtime. This appeared to be installing the same DLLs as in the DirectX Runtime you pointed us to. Once completed and we restarted the application from the IDE, the graphs had the 3D look we're expecting. When we then ran the network version of the executable on this computer, the 3D graphs looked correct.
However, when we uninstalled PowerBuilder 2017 the graphs reverted back to the flat look, although the color settings from the application were being used. (?!) It seems like PowerBuilder is doing something in addition to installing the DirectX Runtime DLLs in order for the application to use the 3D features. Is there a registry entry or some other DLL specific to PowerBuilder that is being installed on the user's computer?
Installing PowerBuilder 2017 on the user's computers or on our servers is not a solution. If we can identify what PowerBuilder is doing in addition to installing the DirectX Runtime DLLs then we might be able to use that going forward.
Any help would be greatly appreciated.