FAM (Fixed Asset Manager)

Forum|Forum|5 years ago
January 22, 2021
8 replies
23 views

Is anyone else having problems getting Fixed Asset Manager (FAM) to work in QuickBooks Accountant Desktop 2021 and Enterprise Solutions Accountant 21.0? The reason I bring it up here is that I cannot get the FAM program to stay open in QB. If I can't get it to stay open in QB, how am I going to export my fixed asset information to ProSeries? There is some problem with FAM in QB every year! Last year, I reported a problem on 2/4/2020. I finally got a call from a "cheerful" supervisor with QB on 4/1/2020, telling me that they had finally gotten the problems with FAM resolved! Too late! I had already had to re-enter every fixed asset item directly in ProSeries for most of my entity returns. I specifically asked this year before I renewed any Intuit products if they had resolved these problems between QB, FAM, and ProSeries. I was assured all was in good shape. Here we go again!

ProSeries Fixed Asset Manager

This topic has been closed for replies.

O

Orlando11

Level 8

I'm very sorry for the frustration. We are investigating and I will update by the end of the day. Unfortunately the interplay between ProSeries & QuickBooks includes Microsoft, so it can be complicated. This sounds like an issue we had with a Microsoft Update that was impacting things in the manner you describe back in September, but it had been resolved and verified. We're looking into if it came back.

In the meantime, what version of Windows 10 are you on? This *might* be an issue with 1809, and it might not be an issue with 1909.. that's what we are in the process of trying to verify.

Also, can you confirm you are on the latest update of QuickBooks *and* FAM? From what I understand when you update you have to explicitly choose to update that component.

(I wouldn't do anything just yet.. just wanted to ask what version you are on)

D

DRBEAAuthor

Level 4

I'm not doing anything until the engineers tell me what to do. The really frustrating part of this is that I reported it over 2 weeks ago. And then, at least 6 or 7 times after the first time. Each time, the technical support people acted like they had it fixed and closed the cases. Therefore, when I would experience the problem the very next time I opened a new client or maybe the next day, I would call back to report the problem again, and nobody knew anything about the previous call. One of them even told me that they didn't see any previous case numbers with this problem. After 6 or 7 times of calling in with the same problem, you would think the technical support people would know to escalate this problem up to the engineers. Each one of them wasted at least 2 hours of my time. Let's see - 14 hours! What could I have gotten accomplished in that time? How much could I have billed out for completed work? The key words are "could have". I didn't get to complete anything, because the program wouldn't work and no one took my calls seriously until now. I'm really upset again - same thing happened last year!

O

Orlando11

Level 8

I'm sorry for the frustration, and will look into the background of how the case was handled as well. Just so that I know where to start, where you working with QuickBooks Technical Support or ProSeries Technical Support or both?

And just for way of introduction, I'm the ProSeries Engineering Manager. I can't say with certainty yet where the issue is or what it is, but that we are looking into right now and any information you can provide will help. To start with, what version of Windows are you on and are you on latest version of QuickBooks & FAM?

O

Orlando11

Level 8

Just closing the loop - the update to the QuickBooks update has gone out. If you get latest QBFam update in QuickBooks you should correctly get - and stay on - the "December" version.

qbteachmt

Level 15

Thanks for the follow up.

Don't yell at us; we're volunteers

Sign up

Login with SSO

Let's get you signed in

Login with SSO