Where does it warn the user of what can change user information? It makes no sense to store this in the registry. Where is the warning? This information should be in disk tables and refreshed at module start/update. You are right I did not move to another workstation, that was the 1st failure 14 months ago and it was only a couple of invoices. No we don't log on to different workstations.

As a programmer of over 40 years, this implementation is "fun" that a programmer figured out how to do and implemented for no good reason. I fired these kinds of programmers for playing dangerous games with my products. This is a management failure and I will probably pay the price for poor management. This feature should be implemented by user-id and follow me at whatever workstation I sit at.

I now know what happened. I replaced my system server-Windows 2000 to Windows 2003. I know that there were significant differences in the management of client workstations based on this change. I planned for these changes and suffered no loss of time or function. But NOT knowing that Adagio, a user program, is storing critical information in the registry is ludicrous and probably has cost me my largest customer.

Again, I am going to request a pop-up similar to the print pop-up showing current email controls before the actual send. It is not reasonable nor should it be allowed to allow an operator to go to the email screen review the email setup for no apparent reason every time we want to send invoices or statements except in the form of a pop-up. Operators are not supposed to be aware of, how to change, or updating things that they are just supposed to use; this update/change feature should be a security restricted function. If things are not as they should be, in a pop-up, procedures should have the operator contact the supervisor for direction. Current implementation of email is great but EXTREMELY DANGEROUS and for me it is going to be very expensive.

I apologize for venting, but this is going to be very expensive for our copmany!