Hi Gene, If you hold off using v9 until ALL the issues are resolved then you may never get to use it. I have been using v9 since the day it was released and have had no more issues than with v8. Legacy has been quick to respond to any problems and, I’m sure, will continue to do so.
You can run v8 & v9 side by side. V9 overwrites the v8 files (without warning) so make a copy of all the v8 files first, install v9, then rename the v8 files. V9 is not compatible with v8 so running them side-by-side is really not practical as they will two separate, non-compatible, databases. I kept the option to run v8 as I still help others who haven’t (didn’t) upgrade but I have never had to go back to it. Just make the switch to v9. Bob Austen From: LegacyUserGroup [mailto:[email protected]] On Behalf Of Gene Wheeler Sent: Monday, July 10, 2017 9:09 AM To: Legacy User Group Subject: Re: [LegacyUG] Problem with V8.0.0.602 and V8.0.0.604 That just seems to introduce another set of issues! I've purchased v.9, but am holding off using it until the problems all get cleared up. I think LFT is maybe getting too complicated to design and use all the new features. IMHO, they should continue to support v.8 for those of us who would rather have a solid, reliable tool and still offer v.9 to those who have more patience to deal with it's issues and can't wait to use the new features. Can 8 and 9 run side-by-side on the same machine? If so, one could use v.8 as the preferred version, and still run v.9 to learn its intricacies before adopting it to replace v.8. Gene On Mon, Jul 10, 2017 at 10:47 AM, ROBERT A SUDDATH <[email protected]> wrote: you nee dto upgrade to latest versions!! Bob Suddath [email protected] denversuddaths.homestead.com _____ From: LegacyUserGroup <[email protected]> on behalf of Chris Hill <[email protected]> Sent: Monday, July 10, 2017 8:35 AM To: [email protected] Subject: [LegacyUG] Problem with V8.0.0.602 and V8.0.0.604 This is for information. I am running Legacy 8 on a Win 7 64bit Ultimate, fully updated by Microsoft and running the Symantec Norton Anti-Virus. About a month ago it got updated to V8.0.0.602. That then likes to display a prompt about upgrading to Legacy 9. Hit Close to ship out and you get a Run-Tine Error 75 message and the program closes. Eventually resolved that as a program combability issue, having raised it as an formal issue and got pointed at the collection of possible causes. I have now been updated to V8.0.0.604 and the same issue occurred. This time I completely removed and reinstalled, and still got the same issue. Ran the program compatibility checks and Windows decided that it needed to be in mode Windows XP (SP2) and it now works. But Legacy 8 came out in 2013, so it should have been compatible to Win Vista, Win 7, Win 8 and Win 8.1. To my knowledge, it is only the .602 and .604 versions that have this issue – certainly I have seen no issues with previous versions. So what have Legacy developers changed for these versions to make then incompatible or have they forgotten to tell the installer to make them needing to be in Win XP SP2. The other alternative is that I am up to date on Microsoft .NET to level 4.6, and have 4.7 waiting for installation. Regards Chris -- LegacyUserGroup mailing list [email protected] To manage your subscription and unsubscribe http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com Archives at: http://www.mail-archive.com/[email protected]/
-- LegacyUserGroup mailing list [email protected] To manage your subscription and unsubscribe http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com Archives at: http://www.mail-archive.com/[email protected]/
