as i am (and probably most of the testers are) admin on the pc, where toad is installed, some privileged access get missed.
i just made the observation, when i manually installed toad 4.6 on a customer machine, he, when he logged in, got a java-stack on startup. it immediately disappeared, when i opend (gave full control to everybody on) the install-dir (C:\Program Files\Quest Software\Toad for DB2 4.6). i can remember, i had to package this in every version i created, so i would bet, this behavior did not change in 4.7. (i haven’t tested …)
could i convince development to have toad working properly, without having to open any dirs under C:\Program Files? in a big company, opening directories is not desired behavior.