Windows 7, 64 bit platform
Normally, we run our main app from a batch file, which consists of:
--- add the Class Libraries
--- add the runtime DLLs
--- add the Help files
--- change the current directory to where the code resides and run the app
Today, out of the clear blue sky, one tabpage of one module in my app started failing when the app was run from the batch file.
If you place all of the required files into a single folder and run the app by double-clicking the EXE, everything works correctly.
By process of elimination, I found that if I put a copy of PBSHR120.DLL in with my application code, everything works correctly even when the app is started from the batch file. This would seem to indicate that the PBSHR120.DLL in the referenced folder is damaged; except that the copy in with the code was copied from the referenced folder. Which would seem to indicate that the DLL is just fine, thank you very much.
1) Replacing the PBSHR120.DLL in the Resources folder. The error still occurs.
2) Creating a new Resources folder, copying all of the required files from a different folder (the Production folder) into that new folder and pointing the batch file to that new folder. The error still occurs.
3) Referencing the production folders instead of the development folders in the batch file. The error still occurs.
4) Restarting PowerBuilder. The error still occurs.
5) Restarting the VM. The error still occurs.
6) Adding the new Resources folder to the PATH variable. The error still occurs.
My work-around is to simply place a copy of PBSHR120.DLL in with my application code.
Any ideas on what might be causing this behavior of this ONE runtime DLL?