|
Posted by Diane Koers on September 13, 2007, 7:55 pm
Please log in for more thread options
Hi Ted,
I haven't had problems with the delay time, but I've encountered lots of
other issues - mostly on networks and due to the new Pervasive engine. Your
client mentioned he needs to change a lot of jobs from active to inactive. I
strongly suggest, rather than do them one at a time, that you show him how
to export the jobs and change the inactve status to True for the jobs he
wants to change. That would be a lot faster.
How's things in Canada?
--
Diane Koers
Peachtree certified consultant
www.thepeachtreelady.com
Co-author Peachtree for Dummies
>
> The following is a communication from one of my customers.
>
> Comments, insights, from anyone?
>
> ____________________________________________________________________________
>
> I'm not sure if you've had a look at Peachtree 2008 but I just
> thought I'd let you know that I'm not pleased with it and wouldn't
> recommend it at this time.
>
> The maintain job/vendor/employee functions are painfully slow. It
> takes 30 seconds to open a job in order to make a change then another 20
> seconds to save it. I've called Peachtree support twice and used their
> chat support line once with no result. Apparently the maintenance
> functions use Microsoft .NET Framework 2.0 and
> our "tech guy" thinks that may be the root of the problem.
>
> I've asked their support people if they've had complaints from other
> users but they keep avoiding the question. I haven't been able to find
> any comments in Google from other users but I'll keep watching.
>
> Hopefully they'll have a service release in the future. It's going
> to take me 45 minutes just to change 90 jobs from active to inactive. Oh
> well, I should have taken your advice about updating every second release.
>
> Regards,
> ____________________________________________________________________________
>
>
>
>
> When replying, please remove from the email address.
|