We have many applications here, but two of thes applications so far will not
open when we are remote controlling a computer. Both of these applications
have one thing in common - they both have different paths in the icon
properties for the Target and Start in. So in other words the Target might
point to C:\Program Files\Application\App.exe and the Stat in will point to
C:\Windows\System32 (this is just an example.) Both Target paths include
multiple switches and one includes an ini file and the other includes the
name of a frm. The developers, instead of putting the full path to these ini
and frm files in the Target are using the Start in path to accomplish this.
When we put the fill path in the Target line to these files, the application
opens fine with Remote Control or without. When we leave the icons as is,
the applications will not open in Remote Control but will open for the user
once we disconnect.
Questions:
1. Has anyone ever seen this before?
2. Is there a document somewhere which talks about the rules for creating
Shortcut properties? I would like to forward this to the developers of these
applications because I don't believe making the Target and Start in paths
different is a best practice.
3. Does anyone have any idea why remote control would prevent these apps
from opening?
I know this is a tough one but I know there are some really good techs out
there. I depend on you guys/gals for stuff like this and I appreciate your
input.
Thanks,
Christine Lisi
Application Specialist
City of Delray Beach
|
Similar Threads
