1. Home
  2. Quicken Personal Finance
  3. Strange x64/Vista problem

Strange x64/Vista problem

I've got Windows XP x64 and Vista dual booting. The other day, I reinstalled Quicken (06, Basic) on the Vista partition. I already had it working fine on x64. As best I could tell, Quicken was working fine on both OSes at first. I could open and save in x64 and then open in Vista and all the stuff I had updated while in x64 is updated in Vista. And vice versa.

Now, however, Vista seems to be stuck on an old Quicken file, missing recent transactions, etc. I even tried opening the Quicken file while in Vista by double-clicking on the file that I KNOW is the working Quicken file and had just been updated while under x64. But it still brings up the old file (without the recent transactions). And when I closed out Quicken in Vista, that file remained unchanged (the date of the last revision remained the same). I could be wrong about this, but I'm pretty sure Quicken saves a file you've opened up, even if you didn't make any changes in the file itself. So the modification date should have been different, but it wasn't.

Anybody have any idea what might be going on here and what I might do to fix things?

I realize a lot of you won't know anything about Vista. I'm just wondering if you've come across a similar problem in the past in which Quicken appears to be opening the correct file, but the data inside is out-of-date. Especially intriguing is the fact I could apparently open and close Quicken in Vista without causing the modified date of that file to change. And yes, I did refresh the folder view to make sure.

I'm also exploring this issue with a newsgroup of Windows experts. If I find out anything over there, I'll let this group know as well.

Reply to
DP
Loading thread data ...

Hi, DP.

How many Quicken folders do you have in your computer?

If you accepted the default when you installed Quicken in WinXP x64, Setup would have installed it in C:\Program Files (x86)\QuickenW. Then, when you installed Quicken again in Vista, the default location would have been D:\Program Files\QuickenW. Your drive letters may be different, but the point is that you would now have TWO Quicken folders, completely independent from each other. In that case, QW.exe running on D: would not be able to see and read the *.ini files - and other configuration data - in the Quicken folder on C:. And it would not be able to update the data in those files.

I've been dual-booting for nearly 10 years, including both x86 and x64 versions of nine builds of the Vista beta and now Vista RTM, and WinXP. And I've installed the current Basic versions of Quicken 2005, 2006 and now 2007 in each of them. I've not had or heard of the problem you are seeing.

No matter which version of Windows/Vista I'm running, and no matter if it is installed in Drive C:, D: or X:, I always install Quicken into E:\QuickenW. That way, the same Quicken configuration files are used and updated every time I run the application. And I let Quicken keep my data files in that same E:\QuickenW folder.

My guess is that Quicken in Vista has no idea what Quicken in WinXP has done to your file - and vice versa - because neither can see the \QuickenW folder being used by the other. It's not an x64 problem, or even a Vista problem. It's a problem with your installation of multiple copies of Quicken.

RC

Reply to
R. C. White

Your approach would be the logical first conclusion. But that is not the case, as I said in my original post: "I even tried opening the Quicken file while in Vista by double-clicking on the file that I KNOW is the working Quicken file and had just been updated while under x64." In other words, both Q installations point to the same datafile. I have now tried going into x64 and going to that particular file in Windows Explorer, double-clicking it and have it open in Quicken with everything up to date. Then I'll go into Vista, go into the same file in the same location in Windows Explorer, double click it and it comes up with outdated information. It's like the two Quickens live in parallel, yet different, universes.

Reply to
DP

BeanSmart website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.