FH file associations

RogerF · Post by **RogerF** » 16 May 2012 16:05

My Windows file associations for FH files seem to gave astray. Possibly this is a side-effect of removing the 5.0 beta version? Is there a better way of reinstating the associations than reinstalling 5.0?

ID:6245

johnmorrisoniom · Post by **johnmorrisoniom** » 16 May 2012 16:11

Find a gedcom file (and/or your FH project file)in your projects folder, Right click on it, and choose open with...
From the list available choose FH from thse avialble (If FH isn't showing , choose browse and locate FH in program Files) make sure you tick the box marked 'Always do this'.

RogerF · Post by **RogerF** » 16 May 2012 16:51

The snag there is the need to repeat the process for .ged, .fh_data, .fh_proj, .fh_lua and probably others.

Post by **tatewise** » 16 May 2012 19:32

Preferably in an Administrator account try the following (Vista & Win 7).
Use Start > Default Programs (on right under Control Panel).
Click Associate a file type or protocol with a program.
Luckily all the FH file types start with .fh... and listed together (.fh, .fh_lua thru .fht), plus of course .ged.
Select each one in turn and click Change Program button as necessary and choose FH.

RogerF · Post by **RogerF** » 16 May 2012 21:02

The only .fh extensions listed there are .fh, .fh_lua and .fh_proj -- the ones that I've previously assigned manually in the manner mentioned by John. Oddly, .ged isn't in the list, although I've assigned it also to FH, and the association works. Picking one at random, .fhdx (diagrams) doesn't appear, and isn't associated with FH.

Is this connected with uninstalling the FH5 beta, d'you know? If so, it's a right pain.

YouTube · Post by **Jane** » 17 May 2012 08:03

It's probably to do with the beta, as I did it on my laptop.

I just used assoc and ftype to fix it.

You can use the following batch file, it does just the fh items.

http://dl.dropbox.com/u/1367679/fhassoc.bat

but if you are not running x64 windows you might need to change the path lines for the FH program before you run it as an administrator.

Post by **tatewise** » 17 May 2012 10:20

Wouldn't it be easier to simply re-install FH V5 over the existing FH V5?
It should simply repair the file associations, but leave everything else untouched, except perhaps the default project folder location.

Family Historian User Group