Thank you for the welcome.
Boy, I don't like that answer!!
I will be going to the site tomorrow so I can try option 3 - I did zero in on that one in this very nice forum.
Late question added: When you do Option 3, do you do it from the admin account or do you do it from the standard user account. On the later scenario, would you do it after assigning admin priveleges to that standard user (then revert back later)?
Larger issue - Big picture question: Do you happen to know exactly, "WHY" is this being imposed in such a brutally frustrating and wholly inefficient and disruptive fashion? If I were developing software and had to accomodate Win 7, I'd surely have to know these rules and plan for them, wouldn't I? As an expert, doesn't it seem to you to be counter-productive: spend all this user time and user effort to broker security only to then have to toss out all security? I understand about having the system be secure - I've fixed dozens of friends and neighbor's computers who got hacked/hijacked. But, as this is my first venture into the world of Win 7, doesn't this brand of "absolutism" seem pretty dumb/lame? And, I have to just wonder what exactly do software authors do now?
So other than option 3, there's no other way around this. May I please ask if you know how programs (again, I'l cite CCleaner for example) set themselves up to run on a standard user account; what are the differences, how are they implemented? Is it in some special way that they're coded?
Makes me want to go to Linux...
Brink - let me ask another question so I can try to sort this out before I go in tomorrow...
If I completely disable UAC (IOW drop that slider all the way to the bottom - forsaking all the so called nice security features and warnings for the needed business application functionality) that disabling action still DOES NOT get around the fact that the standard user has no permission to run this legacy app, right? UAC is simply the messenger - it's really a permissions issue, right? And as such, no matter what I set the permissions to on the folders/shorcuts/executables, it's not going to work! Until the authors of this legacy app create a new Win 7 compatible program, right? It doesn't matter one wit if I installed this with the admin acct - standard users cannot run the app. I doesn't matter in which order the user or app is applied to Windows - standard users do not have priveleges with these legacy apps. I want to understand (because it's so hard to believe we've be painted into a corner...) Running the legacy app in "compatibility mode" should bridge the gap, but for some reason the admin token does not inherit down to the standard user, in this case, right? (See? I've been reading....!)
I'd just like some quick thoughts on this... I do thank you and appreciate the time you spend with us here. It must be a labor of love...