Jump to content
ATX Community

jshtax

Members
  • Posts

    515
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by jshtax

  1. How long does it take you to move from one cell to another on k1 entry and rental property? Are you able to get low enough resources to open more than one return? I sent a return to Kim @ ATX and internally on a standalone (since they do not network) was having it take 4 sec+ to move from cell to cell. I was told the plan is to get it back to the speed of 11 but I personally do not see it happening.
  2. Also being able to open more than 1 return still crashes the system due to low resources.
  3. Did you do any multi state returns or returns with multiple rental schedules or k1's? I have numerous returns like this and moving from field to field in a k1 input or rental schedule could take 4-6 seconds between fields. Also prior to removing the computers from a domain setting(ATX did not test this) it would sit on the date for over a minute prior to moving to the category field. These are the issues I personally had that deal with performance. All the cosmetic stuff like editing letters and adding a multi color screen to the print manager are not on the radar of importance.
  4. I still see issues in 13 that were there in 12. I told the rep I could care less about the "3" assignments as those are childs play and can be worked around by using word. I mean come on who honestly cares if you can put a company logo on a letter or you need to show 50 returns only on a screen at one time. I told them if their customers care about this then they need to take up a different profession. My main concerns in 2012 were the slowness of the software opening return, moving from field to field inside a return, and integrity of the data none of these 3 areas were addressed in the preview release from what I could tell.
  5. Why wasn't I a CAB when I am the one that first told ATX back in January 2013 of their issues with the 2012 software. I reached out to Raven Database company and personally determined the software would not work in an embedded database environment, also determined the 2012 software was not designed for a domain environment, and many other issues. I had a team of developers come to my office as well as the so called President Jason Marx. What exactly are you referring to as being ignored?
  6. And it worked? I was noticing a 3-4 second delay between fields.
  7. Did anyone try inputting data into a K1 or schedule E rental property?
  8. No fingerprint here...received EFIN in 06-07.
  9. The IRS does not care......what have they done to make you think anything different.
  10. And yet they still want to target people making under 150K in their audits. What a worthless organization.
  11. For those that do not completely understand there 2 types of databases: 1. embedded where the database is included in the software like ATX and the software is shared(not supported method) 2. server database where database is pulled out from software. this scenario you install software locally on each workstation and you map them to the database location.
  12. I was told the way ATX is trying to run the database as embedded on a network share is not a supported way of running the new RavenDB. I was told by raven that it would cause slowness issues(some of this was resolved when the CCH developers came to my office and determined the software will not run on a domain and must be in workgroups) and even date corruption issues. We are currently up to 200 clients in 2012 and are finding the slowness we once experienced in the domain has returned to the workgroup. Entering information in the manager screens lags/delays up to 2 seconds before responding to key strokes. Once in a return the program crashes repeatedly for various reasons dealing with .net Frameworks and has lagging/delay issues the longer the program is running. I was told until the database is removed to a server version and not embedded most issues will not be fixed. Also we told program needs release a 64 bit version. Most updates will be just a patch and not permanent.
  13. Tech support may as well be non existent since it is a development problem
×
×
  • Create New...