Pres,

Glad to hear that you were able to find a solution.

john.

At 01:10 PM 12/6/2013, grayscot2 wrote:
>Sherry,
>
>         OK, the solution was to get a different
> richtx32.ocx, put that in system32 and syswow64
> and register both (perhaps you only need one if
> you're running Win7, 32 bit; L8 is 32 bit but
> runs in my 64 bit Win 7.  Which is the required one or do you need both 
> anyway.
>
>         The version of richtx32.ocx I
> originally had from Windows and later from
> Legacy was much larger than the 199 or 200 kb than I found by googling.
>
>         There is no source for downloading it
> in the Legacy article you quote, Sherry, and
> there is a typo in the command given for
> registering in system32--written as systemS32.
>
>         Following is the source of the Richtx32.ocx that worked:
>
>                 "Fix for RICHTX32.OCX Component Error When Running a Program
>
>© Ramesh Srinivasan | Windows Vista, Windows XP | 22nd July 2008
>
>When you run an application which was created in
>Visual Basic 6.0, the following error message
>may occur and the program terminates.
>Component ‘RICHTX32.OCX’ or one of its
>dependencies not correctly registered: a file is missing or invalid.
>
>This happens if the program uses Rich TextBox
>ActiveX Control (RichTx32.ocx), but does not
>include the ActiveX file in the setup package.
>
>To resolve the problem, download RichTx32.zip.
>Unzip the archive and extract the file
>RichTx32.ocx to the Windows\System32 folder.
>
>Note that the VB6 run-time distribution package
>from Microsoft does not include the RichTx32.ocx ActiveX Control."
>-----------------------------------------------------------------------
>
>So now I should be able to use L8
>afterall.  Thank you to Sherry and all those who responded.
>
>
>Prescott Smith                      [email protected]
>============================================================================
>From: Sherry/Support [[email protected]]
>Sent: Thursday, December 05, 2013 09:45 AM
>To: [email protected]
>Subject: Re: [LegacyUG] Black On Black
>
>The Note windows in Legacy are based on Windows setting. You can
>change the font style and color in Options > Customize > Fonts 10.1
>but not the background color.
>
>In the past, the black windows have been related to a faulty
>Richtxt32.ocx file, as shown in our KB article
>
><http://support.legacyfamilytree.com/article/AA-00378/11/Error-Messages-Problems/Black-Screens-in-Legacy.html>
>
>Did you try those steps?
>
>Sincerely,
>Sherry
>Technical Support
>Legacy Family Tree
>
>On Wed, Dec 4, 2013 at 9:28 PM, grayscot2 <[email protected]> wrote:
> >
> >
> >
> > I've described the problem earlier but there
> seems to be no solution available: All the
> Notes portions of views in 7.5 and now 8 are
> black backgrounds with apparently only black
> type available. Technical support can't help.
> Otherwise the program seems to be working fine.
> This is true for Geoff's sample file as for my own.
> >
> > Is there anything in the color or font
> options that might alter this? I've tried some
> combinations but nothing--anywhere--seems to
> change, so apparently I don't know how these
> work. I just need to change the Notes field
> screens themselves not the whole panel or view.
> >
> > ----------------------------------------------------------------
> > Prescott Smith [email protected]




Legacy User Group guidelines:
http://www.LegacyFamilyTree.com/Etiquette.asp
Archived messages after Nov. 21 2009:
http://www.mail-archive.com/[email protected]/
Archived messages from old mail server - before Nov. 21 2009:
http://www.mail-archive.com/[email protected]/
Online technical support: http://www.LegacyFamilyTree.com/Help.asp
Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our 
blog (http://news.LegacyFamilyTree.com).
To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp


Reply via email to