Allan, anyone, have you started testing your 2008 Accountant Edition yet? If so have you found anything you really like or think needs to be fixed?
I was thinking of moving my business books & those of my husband (payroll involved) over to 2008 before moving any clients over. I'd like to know if there are any identified oddities/bugs before doing so.
Tara,
This is so strange. UPS just delivered 5 minutes ago the 2008 accountants edition. I took the product out of the box but have not installed same yet.
I have my Premier copy ready for installation. Since I don't have any clients on 2008 yet I thought I would wait until more have installed it to see if there are any glaring bugs. I know several fellow pro Advisors that have installed their copy but have not had any comments from them yet. Maybe it is safe for me to install my copy.
You always have the option of having both versions on your workstation.
>
You first.
No, you first.
Please, you go first.
Hey, let's let Allan go first.
Joanne
I like that idea. Allen, you go first.
I know that. Up until a few weeks ago, I had 5 versions of QB and 4 versions of PT installed on my machine.
I just had my hard drive reformated and am only installing the software that I currently need. I am in the middle of finishing up a major project for a client and have limited time to reinstall the missing software. That's when I decided that I would install software as a client needed me to. Everyone is currently on QB2007 so that is all that I have installed so far this week.
Maybe I'll have time this weekend. I need to finish sales tax and payroll tax forms first.
It was a smooth installation and since I keep all my versions separate I wasn't worried. I just haven't upgraded any of my existing QB files to actually work in the program.
I remember Allan finding a few issues when 2007 was first sent out to us all so I assume he's got a method for testing functionality rather than just trial and error over time like myself.
Thanks. I got mine about 2 weeks ago. I've installed it & opened a sample file but haven't worked in it.
It was very sluggish in opening the sample file & there was a slight lag to navigation inside the file...as compared to 2007.
I didn't have anything else running so I don't know if that was a first-time sluggishness or if its the new version. I have a P4, 3.4ghz,
2gb ram w/200gb hd, running XP Pro on this particular machine.
QB 2008 appears to be working fine on my Vista workstation. QB 2007 data files did require conversion to QB 2008 format.
The QB help system seems improved but the help window can't be dragged to a second monitor, it is anchored to the window that is open on the screen. Not a big deal but just thought I'd mention it.
"RebelGraffiti":
One possible cause of initial sluggishness is the use of the .net framework in QB. It makes use of a technology called Just-In-Time compilation (JIT). The first time you run an application with code subject to JIT it is compiled, which of course takes some time (usually not more than a few seconds). Subsequent runs use the compiled code and are faster.
"Laura"
Just a warning: I have seen problems with QB versions when an older one is installed after a newer version. I'm not sure if they fixed that in recent years, but you might want to do some sort of restorable drive image before say installing QB2005 after QB2007 -- just in case.
I hadn;t thought about that possibility. I think I usually end up installing them as the new one comes out. Worst case is I use my old laptop that has them all installed if a QB 2005 or 2006 client comes my way. Right now I'm sticking with 2007 and 2008. A new client just popped up yesterday and they are using 2008 so I will be installing that program this weekend.
That would make sense except for the fact that .netframework was required with version 2007 also.
>"Allan Martin":
Do you mean that QB2007 didn't exhibit the same initial sluggishness? Or that since QB2007 also used the .net framework that the JIT compilation already occurred?
If the former, it could be that QB2008 makes more use of the framework. So more JITting.
If the latter, each application has to be JITted -- not the framework itself.
Anyway, I'm just wild-a$$-guessing here :) Could just be the usual creeping bloat.
Or a possible slight trade-off for greater stability and functionality.
"greater stability and functionality"?
Who would have thought that our Mr. Martin was a comedian, in addition to all of his other talents?
I'm STILL laughing at that one - thanks, Allan!
Tony
BeanSmart website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.