Jack from Ohio

Have you read ANY of my posts about the directions?? Or maybe it appears that you simply discount what I say as so much drivel... DON'T MESS WITH IT!!!

Will everyone please forget all that you knew about ATX 2012 and earlier? The password function is by design. It will not activate until you turn on the security function the first time. During the initial setup, the facts about the default username and password are shown.

Hold down the Ctrl button and roll the scroll wheel on your mouse...

You are talking of problems within the separate Fixed Asset Manager. I/we do not use the separate FAM program, so I have no first hand experience with it. As far as your bet, send me a PM and tell me which person at ATX told you it would be fixed and I will contemplate your bet!!

Have you installed update 13.1?

Mercury is in retrograde!!

If you want to use the program on the server, you should have installed it as server and workstation. A choice in the network setup choices. Follow the directions and don't rethink. You CAN run ATX 2013 on the server as well as on the workstations. Admin functions can be done on any workstation.

The server function of the program is not accessible. It will not show in the program listings. It works ONLY in the background doing the server functions. Don't mess with it. Any instructions saying that you can change things from the admin panel for the server are incorrect. Instructions were printed before the last 2 restructures of the program immediately before release. Trust me on this.

Use Admin (case sensitive) and leave the password field blank. Then go in under security settings and set them up the way you want. The username and password ARE case sensitive. Updated.... User Names No Longer Case-Sensitive In ATX 2013, user names are no longer case-sensitive. Passwords remain case-sensitive. For more on setting up user names and passwords, see Adding Users to the System in Program Help.

CCH stopped doing any "fixing" of 2012 in early April in deference to putting all resources into making 2013 a useable product. Send me a message as I have information that can ease your mind about 2013. I will send you a message as well.

WHEW!!!!!!! After months of stewing and stewing around about what my wife wants for Christmas, I finally found her Christmas list. This is going to be easy, here's what's on it. 1. bag flour, 3. cans chicken noodle soup, 1. loaf bread, frozen veggies, coffee creamer, sweetener, shampoo n cream rinse............

Neither ATX 2012 or ATX 2013 are designed for, nor are compatible with terminal server operations. It may have worked in 2011 and prior, but was not supported. Using terminal server to access a program with in the local network is unnecessary and just adds complexity to the process of using the program. In house network should be connected directly. Trying to use terminal services or RDP from a different office location invokes the same issues as well as BEING IN VIOLATION OF THE LICENSING AGREEMENT. Your license is address specific. Bottom line: IT WON'T WORK. No workaround is available.

Another case where you totally missed the main point of my post.

The programs are NOT similar at all.

Very bad assumptions. CCH developed TaxWise. CCH bought ATX. The programs are NOT similar at all.

No problems in either area now. Even before I cleared cache. Well done!! Seems that Microsoft is putting out products early again....

Thank You for paying attention! Now I have saved at least one other user from a bunch of headaches.

Vista is an incomplete version of WIN 7. Buy new hardware with WIN 7. Not expensive. Vista will not support 64bit. Less trouble from now on if you update. When did the ATX technical people tell you that Vista was the same as WIN 7? I doubt it was a technician, rather one of the phone answerers that could only read scripts. Just move into 2013-2014 and upgrade.

Eric, I have IE 11 on all 3 of the computers I use regularly. Not being able to quote only happens on my laptop. However, for the last 3-4 weeks, the formatting options are not available to me anywhere. I will clear cache and see if it helps.

Eric, compared to the HUGE benefits we receive from your work providing this forum, a little down time is only a TINY TINY inconvenience. Thank You for all you do.

RBowersea, Check your messages please.

mwilliams, please check your messages.

The directions were included with the CDs. Clearly marked, and easy to understand. If I communicate directly with a user, I can be sure that the information is followed correctly. Already spoken to two different users that did not follow my suggestions, and had to restart the entire process. You can lead a horse to water.....

That would be a rookie mistake by the person that designed the computer. The idea was, that if the operating system failed on a specific drive, the data on the other drive would be safe. While this may have been a good idea for Win 95 thru Millenium, it is now just an urban myth. I have not seen an operating system fail in 10 years. I have seen hard drives fail. Having two separate drives does NOT REDUCE the chance of either of them failing. The only protection against a hard drive failing is a raid configuration where information is redundantly written on multiple drives, with ability to recreat the data on a failed drive. DON"T MESS WITH IT!!!!