cnccpas

Thanks for letting me know. lol Just wanted to make sure the users were aware the data is not where they specified for it to be installed anymore, most importantly.

unfortunately for lacerte , the massive Inuit giant has devoured them and I wouldn't dare attempt dealing with any product from Intuit. Intuit has screwed GAAP and any fundamental accounting system design and forces their services to your clients in an effort to undercut you. Then they slap you in the face with a "pro-advisor" status and offer their India complete payroll services to you clients. I'm stuck with Quickbooks, but that's enough and that's all they'll get. Played around with Drake (odd interface) and Thompson's Ultra Tax (looks nice would take adjusting) and will spend some more quality time this summer with them.

I have atx running on a dual intel quad core xeon 2.33 ghz with 8gb or ram on a 2 tb raid stripe on a set of 15k RPM drives. if you see my other posts, i can open a 2011 return including the program and searching for client, to the 1040 on screen in 20.8 seconds, first time opening after a reboot. Even faster the 2nd time. I can't even open the 2012 program in that time now. It has -0- to do with hardware and everything to do with the raven database engine and the way the program stores and accesses data. I sent ATX about 4-5 different service request and nothing in return for over a week beyond the automated response. I am currently testing a handful of other tax programs now and while i'll have to limp through this year, another company will most likely be getting our account for next tax season. This release was a total lack of due care for the end user that I have seen from any software company. It was wreck-less and I place it above the Microsoft Windows ME release for all-time fail.

No problem, Losing tons of billable hours thanks to ATX. Just showing my appreciation and I have yet to get a response for over a week "that generally takes 24 to 48 hours" according to the email.

OMG another IT guy that has dissected ATX's blounders. I too tried the different credentials to run ATX, it works but has major issues when working with PDF printers since that process is ran by another process under your original system credentials. The problem is the Raven Database and the idiot usage of UNC mappings. There is a reason microsoft has tried to kill UNC mappings for the past decade. Not to mention, have you located you data yet? heehee it's not where you told it to be. All Usersapplication data or C:program data . nice place and cloud backup services won't touch them.

easy answer to this question and will probably repeat it for every problem. 1. Somebody felt smart and switched to the Raven database system using .net. Basically a total overhaul of the program. Notice they separated the "Payroll" returns from the program? They are still using the old ATX engine and the payroll program is perfectly fine. 2. The raven database is a document-based database and apparently in ATX is using UNC mapping for running the program which causes massive amounts of unnecessary network calls and packet congestion. UNC mapping has been on Microsoft's kill list for years as it is also easily exploited. Those fam with how a particular Intuit product took performance hits when they began using the file monitoring agent (aka license checker) were also victim to this. Since opening a QBW file over a network connection was horrendously slow compared to prior years. It's all in the database calls, SEND, ACK, RCV, that good stuff. However you look at it, UNC mapping is one of the most ill-thought ways to run a program and is an insult to any IT professional. If it was the preferred way of accessing data why has UNC program access been on the security zone block from the OS for years? H-E-L-L-O? There is a reason Microsoft does this. 3. Another thing, the Raven Database is coded to use the Application Data folder under All Users in non Windows 7 and 8 OS, a BIG NO-NO. Notice to all cloud-based backup users, CARBONITE IS NOT BACKING YOUR ATX DATA!!! Windows 7 and 8 users will find their ATX data in the hidden System Data folder off their C: drive, since the true user data folders are system access only and no users can touch. Again, CARBONITE will not seek this out. This is what causes so many multi-user issues too. 4. Simple comparison of 2011 to 2012. 2011 Time to open up the program for the 1st time, search a client name, open the return and see it on the screen, 20.8 seconds. 2012 Time to open the program - 52 seconds 2012 Time to search the client by last name - 1:30 not included 2 prior failed attempts (program crash) 2012 Time to open the same return after the first initial time (don't count rollover time). 3:45 minutes. Simply don't see how the wool was pulled over somebody's eyes in the conference room when somebody proposed this. Unless it involves a cheaper developer software license or the leftover crap from that other tax program they recently bought. Great job though, took a good program and ruined it.

easy answer to this question and will probably repeat it for every problem. 1. Somebody felt smart and switched to the Raven database system using .net. Basically a total overhaul of the program. Notice they separated the "Payroll" returns from the program? They are still using the old ATX engine and the payroll program is perfectly fine. 2. The raven database is a document-based database and apparently in ATX is using UNC mapping for running the program which causes massive amounts of unnecessary network calls and packet congestion. UNC mapping has been on Microsoft's kill list for years as it is also easily exploited. Those fam with how a particular Intuit product took performance hits when they began using the file monitoring agent (aka license checker) were also victim to this. Since opening a QBW file over a network connection was horrendously slow compared to prior years. It's all in the database calls, SEND, ACK, RCV, that good stuff. However you look at it, UNC mapping is one of the most ill-thought ways to run a program and is an insult to any IT professional. If it was the preferred way of accessing data why has UNC program access been on the security zone block from the OS for years? H-E-L-L-O? There is a reason Microsoft does this. 3. Another thing, the Raven Database is coded to use the Application Data folder under All Users in non Windows 7 and 8 OS, a BIG NO-NO. Notice to all cloud-based backup users, CARBONITE IS NOT BACKING YOUR ATX DATA!!! Windows 7 and 8 users will find their ATX data in the hidden System Data folder off their C: drive, since the true user data folders are system access only and no users can touch. Again, CARBONITE will not seek this out. This is what causes so many multi-user issues too. 4. Simple comparison of 2011 to 2012. 2011 Time to open up the program for the 1st time, search a client name, open the return and see it on the screen, 20.8 seconds. 2012 Time to open the program - 52 seconds 2012 Time to search the client by last name - 1:30 not included 2 prior failed attempts (program crash) 2012 Time to open the same return after the first initial time (don't count rollover time). 3:45 minutes. Simply don't see how the wool was pulled over somebody's eyes in the conference room when somebody proposed this. Unless it involves a cheaper developer software license or the leftover crap from that other tax program they recently bought. Great job though, took a good program and ruined it.

easy answer to this question and will probably repeat it for every problem. 1. Somebody felt smart and switched to the Raven database system using .net. Basically a total overhaul of the program. Notice they separated the "Payroll" returns from the program? They are still using the old ATX engine and the payroll program is perfectly fine. 2. The raven database is a document-based database and apparently in ATX is using UNC mapping for running the program which causes massive amounts of unnecessary network calls and packet congestion. UNC mapping has been on Microsoft's kill list for years as it is also easily exploited. Those fam with how a particular Intuit product took performance hits when they began using the file monitoring agent (aka license checker) were also victim to this. Since opening a QBW file over a network connection was horrendously slow compared to prior years. It's all in the database calls, SEND, ACK, RCV, that good stuff. However you look at it, UNC mapping is one of the most ill-thought ways to run a program and is an insult to any IT professional. If it was the preferred way of accessing data why has UNC program access been on the security zone block from the OS for years? H-E-L-L-O? There is a reason Microsoft does this. 3. Another thing, the Raven Database is coded to use the Application Data folder under All Users in non Windows 7 and 8 OS, a BIG NO-NO. Notice to all cloud-based backup users, CARBONITE IS NOT BACKING YOUR ATX DATA!!! Windows 7 and 8 users will find their ATX data in the hidden System Data folder off their C: drive, since the true user data folders are system access only and no users can touch. Again, CARBONITE will not seek this out. This is what causes so many multi-user issues too. 4. Simple comparison of 2011 to 2012. 2011 Time to open up the program for the 1st time, search a client name, open the return and see it on the screen, 20.8 seconds. 2012 Time to open the program - 52 seconds 2012 Time to search the client by last name - 1:30 not included 2 prior failed attempts (program crash) 2012 Time to open the same return after the first initial time (don't count rollover time). 3:45 minutes. Simply don't see how the wool was pulled over somebody's eyes in the conference room when somebody proposed this. Unless it involves a cheaper developer software license or the leftover crap from that other tax program they recently bought. Great job though, took a good program and ruined it.

Fix the program and the horrible new database server. You should not have to do such upgrades. In the end the program should complete a tax return. Not operate a nuclear powerplant or calculate missile trajectory. It is NOT your equipment, it is the program.

easy answer to this question and will probably repeat it for every problem. 1. Somebody felt smart and switched to the Raven database system using .net. Basically a total overhaul of the program. Notice they separated the "Payroll" returns from the program? They are still using the old ATX engine and the program is perfectly fine. 2. The raven database is a document-based database and apparently in ATX is using UNC mapping for running the program which causes massive amounts of unnecessary network calls and packet congestion. UNC mapping has been on Microsoft's kill list for years as it is also easily exploited. Those fam with how a particular Intuit product took performance hits when they began using the file monitoring agent (aka license checker) were also victim to this. Since opening a QBW file over a network connection was horrendously slow compared to prior years. It's all in the database calls, SEND, ACK, RCV, that good stuff. However you look at it, UNC mapping is one of the most ill-thought ways to run a program and is an insult to any IT professional. If it was the preferred way of accessing data why has UNC program access been on the security zone block from the OS for years? H-E-L-L-O? There is a reason Microsoft does this. 3. Another thing, the Raven Database is coded to use the Application Data folder under All Users in non Windows 7 and 8 OS, a BIG NO-NO. Notice to all cloud-based backup users, CARBONITE IS NOT BACKING YOUR ATX DATA!!! Windows 7 and 8 users will find their ATX data in the hidden System Data folder off their C: drive, since the true user data folders are system access only and no users can touch. Again, CARBONITE will not seek this out. This is what causes so many multi-user issues too. 4. Simple comparison of 2011 to 2012. 2011 Time to open up the program for the 1st time, search a client name, open the return and see it on the screen, 20.8 seconds. 2012 Time to open the program - 52 seconds 2012 Time to search the client by last name - 1:30 not included 2 prior failed attempts (program crash) 2012 Time to open the same return after the first initial time (don't count rollover time). 3:45 minutes. Simply don't see how the wool was pulled over somebody's eyes in the conference room when somebody proposed this. Unless it involves a cheaper developer software license or the leftover crap from that other tax program they recently bought. Great job though, took a good program and ruined it.