|
Posted by Mr. Slow on May 21, 2008, 5:15 am
Please log in for more thread options
> "Mr. Slow" wrote:
>
>>> > I have been using Quicken 2001 (UK version) for a number of years
>>> > without a problem, under platforms of Windows 2000, Windows XP Pro.
>>> > and now Windows Vista Home Premium. This latest setup has been working
>>> > quite happily for about 6 months but now, without warning, refuses to
>>> > do so.
>>> >
>>> > The program starts but any attempt to open a *.qdf file fails with
>>> > this error
>>> >
>>> > "Unable to validate your file. Contact Intuit Technical Support"
>>> >
>>> > Sadly, UK versions of Quicken are no longer supported or updated by
>>> > Intuit. The software is obviously fairly old but has always worked
>>> > well, even with Vista. I don't believe this to be a Vista issue - it
>>> > worked just fine for some months before this problem.
>>> >
>>> > I have attempted to restore backups and validate the files, without
>>> > success - same error message. However, the files are not corrupt
>>> > because I can open them in Quicken installations under Windows 2000
>>> > and Windows XP. I have reinstalled the program - no change.
>>> >
>>> > Does anyone have any further ideas, please?
>
>>> Since the program starts, will it let you create/read a NEW Quicken
>>> file?
>
>> Jim,
>> Thanks for your interest. Yes, I can create/backup/restore and read a new
>> file. If I attempt to restore any of my old files I get a message saying
>> that the restore is successful but when I try to open the file, I get the
>> message "Unable to validate your file. Contact Intuit Technical Support".
>>
>> Any clues?
>
>
> You might try running UAC in the quiet mode, or disabling it temporarily,
> to see if that is the cause of your problem. Here is a tool that makes it
> easy:
> http://www.tweak-uac.com/what-is-tweak-uac/
>
>
Jim,
I have always run Vista with UAC disabled - it's far too intrusive for
experienced computer users. I am intrigued that I can create and read a new
file but not any of my old ones. There must be a clue there somewhere!
--
Remove ".invalid" and replace with ".com" to reply
|