The fix in this issue was somewhat straightforward and it was all related to a set of local files that each user has stored in their profile as described below.
Search for drildown.ini (NOTE: One l in drildown ) on the local machine.
Open this file in Notepad, and check the AppSize setting. BE CAREFUL making changes in this file as you can cause more problems than you're trying to fix...but try setting the AppSize to say AppSize=0/0/640/464.
Note: The AppSize appears to be set dynamically by FRx. I observed that when I logged into the system the numbers would change. The above numbers seem to be a good startign point (0/0//640/464).
Location of this file (Note: Change out {insertusername} for the name of the user on the PC)
C:\Users\{insertusername|\AppData\Local\FRx Software\FRx 6.7 folder
Applied fix and it worked.
In a Terminal Server / Citrix environment the two key files (stored under local profiles):
DRILDOWN
FRX
If there is something wrong in either I found that it can cause FRx not to launch although you may get the prompt to login. Once you login you see the FRx Desktop on the taskbar but no program launches as you might expect.
If you have a user that can start FRx in a TS/Citrix environment, and another who cannot. Try taking a copy of the above files from the profile that's working ( C:\Users\{insertusername|\AppData\Local\FRx Software\FRx 6.7 folder ) and moving it to the profile of the user where FRx won't start.