|
Posted by kaplan3jiim on January 20, 2009, 2:16 pm
Please log in for more thread options wrote:
>> kaplan3jiim@example.com wrote:
>>> I am locked out of one of my MS MOney Essentials (2007+) files which
>>> no longe recognizes my sign in ID.
>>>
>>> I also have QUicken 2006 on another computer.
>>>
>>> I see that there is a Money to QUicken data converter available and
>>> have a few questions:
>>>
>>> 1) Can I convert Money Essentials files to QUicken 2006 Deluxe (this
>>> is backward in time)?
>>>
>>> 2) The converter download site has an invalid certificate that
>>> expired 4 days ago. Is it possible that Intuit would let that happen?
>>> The URL appears valid and McAfee advisor claims it is safe.
>>>
>>> 3) If I convert this file, will I be able to open it without my
>>> Windows Live ID and password, which MS Money had required for online
>>> access (and for all access for this particular file)?
>>
>> The problem I see is that any means of converting Money data to Quicken
>> data requires you to be able to open your Money file.
>>
>> There is no straight conversion of the Money data; you either create Money
>> reports and let the Data Converter work on those, or you export from Money
>> to QIF files and import them into Quicken.
>
>Good catch. I missed that part of the problem. I do recall that there is an
>option to log into the MS money file without logging into the Live ID
>account. Certain features are disabled such as account updates, etc, but I
>think basic reporting is still available.
>
>If the OP is locked out because he can not remember his Live ID password
>there is an option to have the password reset. Using Internet Explorer go to
>this site: http://login.live.com/, enter your Live ID and click on the
>"forgot password" link to reset the password.
>
>Another thought is to clear your PC of cookies. I know that I have had
>problems logging into my LiveID webspace and deleting the cookies has cured
>the problem.
>
Thanks for the responses and I will keep them in mind. As it turns
out I was able to solve the issue by opening the most recent backup.
Something in the current file regarding the login ID had somehow
gotten corrupted.
|