Soon, as soon as I get my pc up and running, lol, I will be moving this to a PM. Why? Because there are six people using VIPER. I know three for sure and three others emailed.
Part of the reason I want to move it is because questions about it should really remain among the six including Ed.
Don't get upset at my next comments. I think I have run into that situation, and I am sure (I think, lol) Ed or someone can fix it out. But, I see this happen ALL the time in issues with AC. A lot of users will always blame SQL or AC when it is their network. In your instance that fact that it works on the other computers and not your new one, begs to the fact that there is a network problem or something with the setup of that computer.
Think about it. That is your newest computer. That is your newest VIPER install. My best is their is an issue in the setup. If it were with all the computers, then....VIPER doesn't get many bugs. It is a very tight, well written program with very few updates. Until we had to make it MU compatible, which was actually a good thing, there hadn't been an update or a glitch in months.
We will try to help with more info. Meanwhile, go to the computers that work. Look how they are set up. Look at VIPER and how it is set up over and over.
I still think I remember a situation like this. I can't recall if it were with all of them. I will say that while it is helpful for my receptionist to be able to pull up and print labs, it is only mandatory for VIPER to work with my MA. So, is your new computer your MAs?
