Peter, Just delete it.
Thanks for using Legacy. Sherry Customer Support Millennia Corporation [EMAIL PROTECTED] http://www.LegacyFamilyTree.com We are changing the world of genealogy! When replying to this message, please include all previous correspondence. Thanks. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dr. Peter Wielhouwer Sent: Tuesday, May 27, 2008 1:19 AM To: LegacyUserGroup@legacyfamilytree.com Subject: RE: [LegacyUG] v7 Error 400 Hi Sherry, Thanks for this fix. I copied the earlier version of vsocx6.ocx to my c:\Windows\System32 folder, and it appears to have made Legacy 7 work! (BTW, putting the file in that folder is a different instruction than the directions on the website for error 400.) Also, what should I do with my newer version of vsocx6.ocx (which didn't work with Legacy 6 or 7) but which presumably other programs need? For the time being I've set it on my desktop, so as not to overwrite it with the earlier version. Peter -----Original Message----- >From: Sherry/Support <[EMAIL PROTECTED]> >Sent: May 26, 2008 3:51 PM >To: LegacyUserGroup@legacyfamilytree.com >Subject: RE: [LegacyUG] v7 Error 400 > >Peter, > >There are a couple of different steps. If saving the vsocx6.ocx file from our >website to the c:\Windows\System32 folder doesn't solve the problem, then you >need to save that file along with the Legacy.exe.local file to the c:\Legacy >folder. Normally that solves the problem and should work for v7 was well as >v6. The key is having the legacy.exe.local folder in the c:\Legacy folder >along with the vsocx6.ocx file. > > > >Thanks for using Legacy. > >Sherry >Customer Support >Millennia Corporation >[EMAIL PROTECTED] >http://www.LegacyFamilyTree.com > >We are changing the world of genealogy! > >When replying to this message, please include all previous correspondence. >Thanks. > > >-----Original Message----- >From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dr. Peter >Wielhouwer >Sent: Monday, May 26, 2008 7:51 AM >To: LegacyUserGroup@legacyfamilytree.com >Subject: Re: [LegacyUG] v7 Error 400 > >Thanks for the reply, Gary. >I'm using XP (sp 2); the original vsocx6.ocx version was 6.0.0.52; I copied >the VSOCX6.ocx version 6.0.0.44. >I'll hold off on more changes until Legacy Support chimes in. >Thanks again, >Peter > >-----Original Message----- >>From: Gary Templeman <[EMAIL PROTECTED]> >>Sent: May 26, 2008 10:02 AM >>To: LegacyUserGroup@legacyfamilytree.com >>Subject: Re: [LegacyUG] vy Error 400 >> >>What operating system are you using? What was the version number for the >>vsocx6.ocx file before you tried the fix this time? Finally, when replacing >>DLL or OCX files, sometimes they need to be manually registered. Follow >>these steps for Windows XP. >> >>1. Once your Window's operating system has loaded completely, click on Start >>and then click on Run. >>2. Next you will input in the Run field a command that tells your computer >>to register the DLL or OCX file. You will need to input specific information >>including the path and the file name. The following is a template for the >>command: regsvr32 "\FileName.dll" >>It is important to note that path is the actual location or directory of >>where the file is located. Filename is obviously the name of the DLL or OCX >>file you will be registering. Below is a sample command: Regsvr32 >>"C:\Windows\System32\example.dll" >>3. Once the command is input into the Run field correctly, press Enter. Once >>the DLL has been registered, you should receive a confirmation in the form >>of a pop up box. This message will list your newly registered DLL file and >>confirm that is was successfully registered into the registry. >> >>There may be a similar issue if you need to try the second fix with the >>msvbvm60.dll file. However I would wait to hear from support before trying >>any of the v. 6 fixes with v.7. It may be a similar problem but need a >>different file version than that posted for v.6. >> >>Gary Templeman >> >>----- Original Message ----- >>From: "Dr. Peter Wielhouwer" <[EMAIL PROTECTED]> >>To: <LegacyUserGroup@legacyfamilytree.com> >>Sent: Monday, May 26, 2008 5:05 AM >>Subject: [LegacyUG] vy Error 400 >> >> >>>I installed v7 from CD, but whenever I attempt to change a bit of >>>information on the individual info screen, I get the error message "Error >>>400- Form already displayed; can't show modally" and then Legacy crashes. >>> >>> This happened to me with v6 as well, and I fixed that using the first >>> process described at http://www.legacyfamilytree.com/helpError400.asp, and >>> I tried that with v7, but the v6 fix didn't work with v7. Before I try the >>> second fix, I wondered if there is a different fix available for v7 >>> specifically. >>> >>> Thanks in advance, >>> >>> Peter > > > > > >Legacy User Group guidelines: > http://www.LegacyFamilyTree.com/Etiquette.asp >Archived messages: > http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ >Online technical support: http://www.LegacyFamilyTree.com/Help.asp >To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp > > > <>< <>< <>< <>< <>< Peter W. Wielhouwer, Ph.D. Mattawan, Michigan, USA Email: [EMAIL PROTECTED] Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages: http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages: http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
