Lee B

Just a clarification. This workaround was posted as a postscript to the 12.16 update instructions. You actually had to scrollown to see it. It was not openly posted on the ATX board or on their important notes that show up on the page before the ATX Community. It's almost like they didn't want to draw anyone's attention to it. Very very strange.

ATX posted this workaround for 12.16 crashes this afternoon Updated 5-17-2013 ATX2012 crashes (displays the long stack error then closes) when printing returns after the 12.16 update. Work-around: Run 'check return' right before printing the return. If any changes are made to the return (even tabbing through fields), you will need to run check return again before printing. SOLUTION: This will be fixed in version 12.17, planned for early June

Posters on the ATX board are also reporting crashing and the backup/restore function is still hanging up the program. More of the same !

We are finalizing a solution for this. We are in the final stages of completing the 12.16 release that will correct the backup issue generated with the 12.15 download. Kim Manuel VP - Customer Relations

The Webinar that I signed up for about CWU on May 22nd and all the other May Webinars are free unless you want CPE Hours, then there is a $19 fee for CPE.

You can sign up to attend Webinars or to view online tutorials for free at www.DrakeETC.com.

You can sign for Drake Webinars or view a long list of online tutorials for free at www.DrakeETC.com.

Several years ago, my state of Oregon had a tax amnesty program, which waived all penalties and reduced the interest by 50%. for all nonfilers who filed and paid all the taxes due. I ended up preparing ten years of C Corporation returns for a client.

This morning on the ATX Blog & board, ATX admitted that program was getting hung up in midst performing backups. They say they have identified the problem and are working on a patch for the users who have already updated to 12.15. Then they will redo the 12.15 update. I am now going to delete my copy of the update, which I didn't install. More of the same.

I am a one person operation running on a standalone, so some more knowledgeable people than me will have to interpret this jargon. While I had minimal problems, this is the final confirmation for me, that it's time to leave ATX.

Good morning, Here are some Q&A's on the Raven Database. What is the purpose of RavenDB in ATX2012? RavenDB is used to provide information to some of the data grids in the application, like the Return Manager and E-file Manager grids. RavenDB is not used in any way to compute the tax return. In what mode or manner is the RavenDB used? ATX is using RavenDB as an embedded database, in embedded mode. In order to use RavenDB in this manner in a way that is supported by RavenDB, there are a couple of implementation rules that must be true. 1) The database can only be opened and used by a single instance of ATX2012 at any given time. This requirement is adhered to by ATX2012. This limitation is one of several reasons that opening ATX2012 under multiple different Operating System Users at the same time is not supported. 2) The database that is opened by ATX2012 must be stored on a drive that is local to the computer that is running the application. This requirement is also adhered to by ATX2012. There are installation scenarios where a database created and used by an instance on one computer may also be seen to be available across the network. However, in this situation, when the application is being run across the network, ATX2012 creates a second database instance that is local to the computer where the software is executing. On a Win7 OS, this local database is found at %SystemDrive%ProgramDataCCH Small Firm ServicesATX2012Data” ATX2012 was never implemented to permit sharing of the database across multiple ATX2012 instances OR to make use of a database that was not found on drives local to the computer that the software is running on. In response to several statements on the community board about the vendor confirming that we are using RavenDB in an unsupported manner; We have been in contact with the RavenDB vendor and explained that ATX2012 opens the database local to the computer AND that we do not support the use of the software from multiple OS user accounts at the same time or in a Terminal Server/RDP or Remote Desktop scenario. After explaining the above unsupported environments, and detailing how ATX2012 makes use of RavenDB, the vendor confirmed that based on his understanding of how the application is making use of the software and of the lack of our support for the RDP/Remote Desktop scenarios, ATX is using RavenDB in a supported manner. Thank you, ATXMichelle I guess that anyone on a network now knows exactly what they are going to get for 2013.

Yeah, I skimmed that announcement. The gist of it seemed to be that anyone who had a IRS isued EIN was obligated to keep the IRS informed of any changes.

I have been using the program and I am at 12.13, which the program still considers to be current. I have auto update turned off. In order to get 12.15, you still have to go to the download center.

According to the new issue of CPA Practice Advisor, ATX declined to participate in their annual review of Tax Software. If ATX is going to have software for the 2013 tax year, you would think that they would want to be included ?

I took a look at Agile Tax. It looks appealing. I was in the midst of arranging a demo. Fortunately, I had an honest rep. She told me she wouldn't sell it to me or anyone else because it had a lot bugs etc.

I have actually written 3 or 4 of these letters over the years, but only when I was doing writeup, payroll and tax prep for the client for more then 10 years in a stable situation, where there was no questions. In your situation, I would not write the letter.

Ken, After givings your post some thought. I am a little bit encouraged by your post. However most people when confronted by upset customers are going to be contrite and say things that will reassure you that everything is going to get fixed. So far, I haven't seen or heard anything else that reassures me. So I am going go ahead with a thorough demo and review of Drake. Frankly, I don't really want to change, but crossing my fingers and hoping that a miracle will occur isn't the way to prepare for next tax season.

On the ATX board, some posters are reporting backup issues since updating to 12.15. 1. One poster reported that upon closing the program, it backed up every return, which took over a hour before it closed. 2. Another poster upon closing the program left it running overnight, it was still hung up in backup, when he came in this morning. You may want to turn off auto backup to avoid this potential problem.

One of the posters on the ATX board said this morning that he was able to negotiate Max for $795 a year for three years, basically one year free. He hasn't decided what to do. He did say that he paid $1,245 last year. My renewal quote last year for Max was $1,249 before discount.

ATX is not going to apologize. They are not going to offer big discounts. Their position is that it was a solid decision to rewrite the program using the Raven Database and that the problems that some users had was due to firewalls, antivirus programs etc, etc. So everyone will have to decide whether "more of the same" is good enough.

ATX did not designate 12.15 as an automatic download, so you have to go to the download center and retrieve it manually.

According to the first poster on the ATX board, who installed the 12.15 update this morning, "Crash" This poster finally is able to open returns on his workstations, but cannot open any returns on his server. Several posters with standalones are reporting to be OK, with no improvements noted.

Just updated to 12.13. Stayed at 12.11 for a long time because it was working well for me. On my 2 G XP standalone, the program takes about 90 seconds to open the first time each day. During the day, when I close the program and reenter, the program opens in about 30 seconds. Client time to open varies from 15 seconds to 60 seconds depending on how complex the return is. After using 12.13 more today, the forms loading in the Print Manager is significantly faster and the lag moving between entry fields is less.

I am attending one of Drake's seminars next month, plus downloading their software etc. I need some feedback on Drake's capabilities to handle payroll forms and efile payroll forms Any input would be greatly appreciated. Thanks, Lee Barckert

It's there and I've been using it since April 15th with no problems.