I have a VB app that works on a Win 2k station with
strict corp. IT control. I was administrator when this
PC was set up and this app was installed. It requires 3rd
party services (custom print spooler for enterprise bar
code printers). That required the administrator password
to set up.
Now I trying to get the next version of my app to work.
The user only has a "Limited" account, but was able to
run the setup.exe under the administrator account. The
operator of this app can only use it with her "limited"
rights. I did set all folders to allow her full rights
while I had full control.
I have a home system with Win 2k set up as close to the
client machine as possible and I could only run with I
set the operator up as a "Power User". BUT the errors I
got on this machine are different than I get on the
clients machine.
Since I can't install VB6 on the clients machine I can't
trace to problem too far and the error messages don't
make sense. Some point directly to restricted rights
problems others invalid MS Office objects (I am
automating Excel) and these error messages make no
sense.
So I guess the question is, Is there any tools I can use
to trace the problems or must I just lobby to get the
Corp. IT policy changed for this workstation?
PS the app was developed on an XP pro machine and I have
limited the setup so to not replace any 2K dll's.
|
Similar Threads
