Re: Menu Bar

On Sat, 28 Jan 2023 13:58:22 -0800 (PST), John Pollard
<[email protected]> wrote:

>On Saturday, January 28, 2023 at 2:11:46 PM UTC-6, Ken Blake wrote:
>> On Sat, 28 Jan 2023 11:59:07 -0800 (PST), John Pollard wrote:
>
>> >Did you make sure Quicken could not access the internet during that install?
>
>> No, I forgot to. Was that important? If so, I'll try it again, probably tomorrow.
>
>Normally, for the purpose were discussing here: Yes.
>
>The idea is to get rid of your currently installed version (release) of Quicken 
>(that's the uninstall part), then install an older version (release) of Quicken.
>You want a release that is old enough so what ever patch file you want to apply 
>will work. If, for example, you were to re-install the same version (release) of Quicken 
>that you previously had, you would not be able to patch to the current release. So, for 
>example; if you have R44.7 installed and you run the patch file for R44.7, nothing will happen.
>
>One of the purposes of that exercise is to insure that the release you end up with is installed 
>by the downloaded patch file, NOT installed automatically by Quicken. Sometimes that auto-install 
>process creates a problem, and sometimes that problem can be corrected by reverting to an 
>earlier release, then running the Mondo patch file (for R44.7), that Mondo patch file would be
>named QW27.1.47.7MPatch.EXE (where the M stands for Mondo). When Quicken upgrades the 
>release automatically, I do not believe it uses a Mondo patch.
>
>> >If you could not access the Menu items after that recent install, 
>> >right-click the downloaded Quicken.exe install file, choose Properties > Details. 
>> >What "Product version" is displayed?
>
>> 27.1.44.28. 
>
>> An old version, 
>
>Yes, and just what you want, if you are intending to upgrade to release R47.7 
>(or any release later than 44.28)
>
>> so even thought I didn't disconnect the 
>> Internet, it apparently didn't do an update . 
>
>I agree. Preventing Quicken from accessing the internet during the install process 
>is just intended to guarantee that no auto-update takes place.

OK, so even though I didn't do it, it's OK?


>
>> Should I do an update now?
>
>If you now have R44.28 installed, and you have not already tested it to see whether
>it exhibits the same problem we're discussing; you should do that first.  

Yes, same problem.


>And if you've already tried using R44.28 with your regular Quicken data file, and you're 
>seeing the same problem, there's still another test you can do. 

>Try using a Quicken data file that has never been opened in the release 
>where you first experienced the problem - presumably R44.7.

You mean 47.7?

>To find such a file, look for the most current backup you know has never been exposed to R44.7; 
>make a Windows copy of that backup in some Windows folder 
>where it will never get confused as a file you want to use regularly. 
>Rename the copied file to remove the "-backup" from the file name (making it 
>indistinguishable from a regular Quicken file). 
>Then open that copied/renamed file with R44.28 to see whether the problem still exists. 

OK, I'll see what I can do (maybe tomorrow)


>Presumably that file will have no corruption - however, I would also consider that you 
>may have had some relatively minor corruption in your file for some time, 
>and that when R47.7 started using that data, it turned minor (previously unexperienced) 
>corruption into more serious corruption.

I suppose that's possible, but it doesn't seem likely to me.

>In any event, at the end of the day, the idea is
>1.) To try to determine whether R47.7 caused the problem, though 
>I think the best we might conclude is a maybe yes or maybe no. 
>2.) To try to find a Quicken release that will not exhibit the Menu problem that
>you can run until a better idea comes along.
>
>Also note: there are quite a few Quicken releases that are newer than R44.28, yet 
>older than R47.7. If R47.7 was the source of your problem, any of those intermediate 
>releases might work, and might be better than R44.28. There should be patch files for
>all those releases at the quicknperlwiz site you used previously.


Sounds like a lot of work to try them all, and I don't expect any of
them to work, but I'll see what I can do.