Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

7.6.200: news

Status
Not open for further replies.

MacolaHelp

Instructor
Mar 19, 2003
659
US
We heard they are fixing the printing problems in 7.6.200 by rewriting the functions in days not weeks per the 9/16 conference call. If they are successful, is there anything else to beware of? I've got a number of payroll sites to update before year end & some have enhancements as well, so I'm getting really nervous. I know some of you have posted your experiences already, but the threads have disappeared. Any new info (since Sept 1 or so) would be great.
 
I was on the conference call the other day, and at a conference with Chuck Riley this week. I believe that year end updates to PR and AP (if any) will only be available for 7.6.200, though no-one seems willing to commit to it...

If that's the case, I have a lot of work to do prior to year-end. Days was what I heard in the conference call too.

Peter Shirley
 
Per the website (9/17 document), if employees exceed SS max or have stock issues for W2 reporting, they must go to 7.6.200. Macola won't release or correct anything but 7.6.200 since the cost to use the old compiler is prohibitively expensive.
 
I just converted a client to 7.6.200 last week. The payroll check gets completely hosed during the update, even though I am using the June CD and not the January CD. Exact had to email me some new files including a maccom.dll, and it was an easy fix, but be prepared.

Other than that issue we had nothing serious.

Software Sales, Training, Implementation and Support for Exact Macola, eSynergy, and Crystal Reports
 
During the upgrade to 7.6.200 are the customized screens still being hosed up as well? I believe I remember this to be an issue and since our site has heavily modified forms, going back and manually re-creating them is not an option.

Please advise.

Andy

Andy Baldwin
 
We had no problems with the customized screens, but be sure and use the June 2003 update.

For whatever reason Exact has decided not to actually give it a separate version or release such as 7.6.200a. You need to look at the dates of the executables and .zip files to determine this.

Software Sales, Training, Implementation and Support for Exact Macola, eSynergy, and Crystal Reports
 
We have never received the 7.6.200 CD's. I need to come up with those.

Andy

Andy Baldwin
 
Can someone post in this thread to let everyone know when the printing fixes are available from Exact? The only place it is an issue for us is with printing shop packets, but that is a pretty big deal. They can only be printed to a printer that is directly connected to the PC. Try to use a network printer (of any type/brand), and after 1-2 packets a Spool32 error is generated and the user has to reboot.

maknight71
 
Thanks DG,

I would also like to see the posting here when the fixes are done. I think Macola is double-dribbling when it comes to 7.6.200(sp whatever) by saying that you have to update by the end of year, yet a major piece to manufacturing companies (printing packets etc) is documented not to work.

Thanks

Andy

Andy Baldwin
 
The "MUST" update, in my opinion, is only for those that use payroll. There will be no update on any versions prior to 7.6.200 due to the Fujitsu/Microfocus compiler issue.

If you areusing Payroll , you must update to get tax tables, hence you must be on 7.6.200 code.

All others can most likely stay safe where they are on 7.6.100a.

Software Sales, Training, Implementation and Support for Exact Macola, eSynergy, and Crystal Reports
 
There certainly are things in 7.6.100a that are "broken", such as forms like acknowledgements not printing second line of description if the page break occurs before the 2nd line on xp clients using impact printers. These are all supposedly "fixed" in 200, but they are rewriting 200 to behave more like 100a, so does that mean we get to see these problems recur? Is it safer to use broken 7.6.100a printing or take a chance on 7.6.200 "reinvented" printing? We were promised this re-write would occur in days, not weeks, on 9/16. Anyone have any new info on the progress of this effort?

If you are a paid maintenance customer & you can't update for fear of taking your system of record down, how do you cost justify continuing to pay maintenance of 10% retail?

It's unknown as yet if there will be any changes to 1099s, but those of us w/PR are going to be on the bleeding edge again. Will keep you posted as to the results. Can say, though, that I'm not excited about being in this role.
 
One of my customers is in the process of testing the print driver re-write. The re-write is suppose to mirror the print drivers used my Exact in the old 7.6.100 micro-focus code. I do not know if they have implemented the new code set but it was delivered several days ago.

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top