Reflection 7 does not work with Windows 2000

[zoby]

Hi everybody,

I would like to know if someone knows the possibility to force Reflection 7 to work with Windows 2000.
I know that this software is not supported neither by WRQ nor by Microsoft, but I notice something :

After I have installed Windows 2000 Pro then Reflection 7, there is a problem which prevents Telnet Connection to be launched (a VBA error : vba not installed, re-run setup). But if I upgrade a NT Workstation (from which Reflection 7 is already installed) to windows 2000, miraculously it works.

Have someone got an idea about that ?

Thanks in advance for your answers.

 

[wapowell]

We use Reflections where I work. Are you using Reflections for IBM? (as400/mainframe?)
We are running Reflections 7 for IBM on many win2k laptops.
On most of the desktops we are going with Reflections 8.
We have applied SP2 and all critical updates to win2k.
I have done several Reflections 7 installs and they all have gone in fine, and are working great. The only issue we have seen is that for Reflections 7 to work on the laptops, the users had to be power users. Otherwise they were getting OLE errors.
I have deployed Reflections 8 on a desktop fora user to test out, and everything came out fine. He was a regular user, no additional rights had to be granted.
How are you installing it? Make sure you COMPLETELY remove Reflections before trying to reinstall it. Also Make certain you are logged in as admin when you install it.
What is the security level of the users trying to run it?

~Bill

 

[zoby]

Reflection we are using is Reflection 7 for Unix and digital. When we launched Reflection with admin rights it works but as soon as a domain user launch Reflection it sends a vba error. The security level of the users is only domain users. When I re-install it I completely removed it and I have got admin rights so I don't see where can be the problem.

What's your point of view ?

 

[wapowell]

You mention that they are "domain users". You don't have to be a domain admin to run it. What are there local rights? Try adding them to the power user group on the local machine they are using, not the domain power user group.