Re: Menu Bar
John Pollard <[email protected]>
| Newsgroups | alt.comp.software.financial.quicken |
|---|---|
| Message-ID | <[email protected]> |
On Sunday, January 29, 2023 at 9:12:04 AM UTC-6, Ken Blake wrote: > This is getting stranger and stranger. I just did what you (John > Pollard) suggested and copied and opened an old backed-up document > (11/30/2022). The problem remained. > > I then deleted that copied backup, shut down Quicken and started it. > It asked me to choose the file to open (it usually doesn't ask, just > chooses the current file, the last one that was closed). I guess it > asked because the last one that was closed no longer existed? > > I chose the current file and it opened it. Lo and behold! The menu > bar worked. Why did it work with the current file but not with the > 11/30 file? Might it have something to do with being asked what file > to open? > > I checked in Help/About Quicken. It was running 46.12. > What happened to 47.7, which is what I thought I was running? Remember, we were never able to confirm what release you were running. I would say that when you reinstalled but did not block Quicken from accessing the internet, your install was for R44.28, but because you did not block internet access, Quicken automatically upgraded to 46.12. > I then went to Help/Check for update and get 47.7. > > The message I got said I had the latest version! Just because the R47.7 patch is available, does not always mean that it is the "latest" (or "current") version for all users. When a patch is first released, it is only available for a small subset of Quicken users - those users act as sort-of post-release testers. If those post-release users have serious issues, Quicken may pull that release; otherwise, Quicken will make that new release, the "latest" (or "current") release. During the time that the new release is restricted to that small subset of users, all those using the most recent previous release will be told they have the "latest" release and Quicken will not install that newer release automatically. > I then did a web search on "quicken update" and saw that 47.7 was > listed there. I'm tempted to install it, assuming that if it made the > problem recur I could redo what I just did. > > Do you think I should try that? It's up to you. But before you do, save that downloaded Quicken install file. I also suggest you take a few fairly simple steps that might aid you if you have another experience like this one. - Create a new Windows folder to hold files you will NEVER use directly - From Quicken, create a New Quicken data file in that new folder (give the Quicken file a name that describes it and suggests you never actually use it such as: "NEW-Never-used-Never-use", ... whatever name you like, to help you remember). If, in the future, you are ever unable to create a New Quicken file for testing: - copy "NEW-Never-used-Never-use" to some other folder where you will test - give the copied New .QDF file a name informative to you about the test you're going to use it for - then use the copied .QDF file for your tests - you can usually expect to delete the copied New file when you finish testing That way you can always use a New Quicken file for testing (or any purpose), even if you can't always create one from within Quicken. If you do the above before you upgrade to R47.7, you will be able to test R47.7 in a New Quicken file. > And why does Quicken Help/Check for update say that 46.12 is the > latest version, but the web site says there's a 47.7? See above.