Got a bit of a problem packaging SAP GUI 7.10 (and patch level 7) with ThinApp - can't open .SAP files directly.
We have entry points being SAPlgpad.exe (the SAP Login Pad - we've also done all of this with SAPLogon.exe instead as well), SAPgui.exe and the primary data store being a large .dat file, merged intsallation type, on Windows XP SP3, everything patched and up to date.
We can start SAP and run it correctly - so we startup via the SAPlgpad.exe and everything runs fine - can connect to the server, input information and do everything we need to do. If we click and DRAG the .SAP file into an already logged in instance of SAP then it executes correctly.What I believe might be happening is that when we run (double click or execute) a .SAP file, it loads up SAPgui.exe (like it's supposed to), then realises that the user needs to be logged in, so calls SAPLgpad.exe to login the user before executing the .SAP file. However, ThinApp seems to be passing the .SAP file directly to SAPlgpad.exe instead of passing a request to login the user. SAPlgpad.exe then doesn't know how to execute a .SAP file and so quits with an error.
I've logged a support call with VMWare about it, but I was wondering if anybody else had packaged SAP GUI 7.1 before and had anything similar to this problem, or whether it was just an issue with our setup?