Default program for ...OFX.DAT file?

Keith - maybe I'm not following you, but why do you think you need to associate '.dat' with any *Quicken* program? I think that those files are used when you are executing the main Quicken executable (.exe) against a main Q data file (*.qdf). What benefits, if any, associating a *.dat would you derive via some form of Quicken association? It's not like you can double click any of those to bring some program up, right??

You might want to take a look at this. Since Q2010 Quicken merged a number of there files into one.

Changes to Quicken 2010 for Windows data file structure Updated: 10/08/2009 | Article ID: 7497

"Keith Snyder" wrote in news:fZf3o.30830$ snipped-for-privacy@newsfe16.iad:

The only dat files I have are log files. Q2010 merged all real datafiles into 1 *.qdf file. Good thing that storage is cheap nowadays, with all the backups I make.

Quicken uses *lots* of .dat files; many in various folders in Documents and Settings, others in Program files.

I think you're right. It's just my fussiness.

Anyhow I did remove extension .dat from association with any program with no apparent ill effect.

Admittedly, I think it is lame that many applications use the *.dat extension...they ought to name that something meaningful regardless of what it is for. After all, in a sense, ALL files that aren't executable are

However, perhaps there is some official (or unofficial but used by everyone) that states that a *.dat file naming convention can be used by an app that needs some data store for whatever reason somewhere, and this is a Windows convention? Ergo, no association needed (or even desired). But each program better beware of where these are stored for their own use. Probably another Windows function that states such a file is created in some directory, perhaps where the .exe is located, or a folder one level below or something.

I don't know enough about Windows programming for this.