Legacy Family Tree fails to run on Vista BETA 2 5384

[Guest]

Attempting to run Legacy Family Tree v.5.0 or v.6.0 fails with the following
error message:

==========================================
LEGACY
==========================================
Run-time error '339':

Component 'COMDLG32.OCX' or one of its dependencies not correctly
registered: a file is missing or invalid

=====
= OK =
=====

I have already contacted the developer, Milennia, and have followed the
directions at http://www.legacyfamilytree.com/helpDLL-OCXerrors.asp to no
avail. I am not necessarily expecting anyone here to correct this problem,
but am more interested in making it known that this issue exists. Of course,
if anyone has seen this and knows how to correct it, I would be very greatful
in knowing the solution.

As a side note, this problem does not and has never occurred (at least for
me) on any version of Windows XP.

 

[Andre Da Costa [Extended64]]

Its best you contact the developer about Vista support and find out if there
are any plans for updates or patches to existing versions of the program
that will support Windows Vista.

You can file a report on the issue in the mean time:
For Feedback:
http://go.microsoft.com/fwlink/?linkid=55160

Feedback reporting tool:
http://go.microsoft.com/fwlink/?linkid=43655

--
--
Andre
Windows Connected | http://www.windowsconnected.com
Extended64 | http://www.extended64.com
Blog | http://www.extended64.com/blogs/andre
http://spaces.msn.com/members/adacosta

 

[Guest]

It is my observation that certain programs will cease to work as you are
dealing with a different OS language. Case in point is that Norton Anti-Virus
2006 will NOT work on Vista. Mind that this is a BETA it is not intended to
replace your current operating system it is meant to only be a test. There is
probably nothing that can be done about that particular program unless the
vendor release a fix/patch or releases a new title all together.

 

[Guest]

I am fully aware of the fact that this version is not intended to replace the
OS on my primary pc, which it has not. I was merely reporting this issue to
MS. If someone else had run into it and found a way around it all the better.