Solved Access not displaying properly

adhoustonj, here is Computer\HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\16.0\Access\Settings

Reg 16.jpg
 
adhoustonj, here is Computer\HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\16.0\Access\Settings

View attachment 113340
That is Computer\HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\16.0\Access\Settings\CommandBars if you look in the file path address bar up top.

How about just: Computer\HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\16.0\Access\Settings
And also ------ -Computer\HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\11.0\Access\Settings

I think Access2003 might only utilize 11.0 - but I'm not certain. Only referencing some microsoft docs.

  1. Locate the following registry key, as appropriate for your version of Office:
    2007 Office suite
    HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Common\Open Find
    Office 2003
    HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Common\Open Find
    Office XP
    HKEY_CURRENT_USER\Software\Microsoft\Office\10.0\Common\Open Find
 
adhoustomj, is this what you're looking for
Reg Access 11 Settings Open FikeName.jpg


Reg Access 11 Settings Open View.jpg
 

Attachments

  • Reg Access 11 Settings Open.jpg
    Reg Access 11 Settings Open.jpg
    39.6 KB · Views: 176
A2003 is discontinued. MS lo longer supports the product
I am well aware of this, I also got rid of Access 2003 when it was time...

Nevertheless, it is possible that your Office/Access setup is older than the latest service packs and patches provided by Microsoft at the time, especially now that you have reinstalled it.

Have a look here (SP3):

And here (several pages with patches for different Office 2003 products):

It wouldn't be the first time that updates fix bugs...
 
maybe it's with your VB6 code that has problem?
 
My VB6 programs that use A2003 are working correctly. I can read records from the DB, add records to the DB and delete records from the DB using VB6. I really don't think that VB6 is the problem.
 
The catalogs listed by Ahayne are dated 2012 and 2022. The DBs stopped opening correctly about 2 months ago.
 
Why don’t you upload a ‘ not working’ db to the forum - we can see if opening in a later version provides any clues
 
OK, I will do it, but I already said that on the other WIN10 computer, it works just fine.
 
The catalogs listed by Ahayne are dated 2012 and 2022. The DBs stopped opening correctly about 2 months ago.
Ok, I'll try again.

The version/patch level of the Access 2003 version you have now installed may be older than the service packs/updates released by Microsoft at that time.

You could therefore use these 'old' service packs / updates to upgrade your installed Access/Office to a newer version, which may have fewer errors and/or security holes.

Note: Even if it may not help to solve your current problem, you should try to install them.

I hope my intention is more clear now.

Addendum: Especially if nothing obvious helps, you should start to rule out possible less obvious sources of error. At least that's how I always proceed.

We are only trying to help you.
 
One more: As you say you have two Windows 10 pcs with Access 2003 where only of them has the described problem.

Did you compare the Access version on both computers? Are they different? Especially the part "(11.8321.8405) SP3" like in the sample screenshot should be compared:

Sample.png
 
Well this is very troubling. I don't know how this could have happened. But the error still could not be explained due to the timing.

Not Working Computer: Office Access 2003 (11.8321.8405) SP3
Working Computer: Office Access 2003 (11.5614.5606)
 
Is it only running on the unpatched computer? Funny.

You could do a cross-check and install the updates on the computer where it is running. :p
 
Those numbers tell the story. The computer that works is missing one or more patches that were installed on the computer that doesn't work. Therefore, (taking a huge inferential leap) it is service pack 3 on the not-working machine. I'm going to lay very good odds that it is FAR too late to back out SP3. The way that Windows Update works is that they keep copies of the files that were replaced in the last patch just in case you need to do a rollback. But those files "age out" and eventually are deleted by a Windows cleanup operation. You can check the system's update history (it's a link off the System Updates page) and if you see an SP3 in the list, you could TRY to roll it back. However, I'm inclined to say this is actually an interaction with SP3 and another patch that seems innocuous. And worse, if the patch in question has aged out, you are just flat-out stuck. What we used to say in the Navy computer group, "OBE" - overcome by events. The polite way of saying":poop: happens."
 
Well this is very troubling. I don't know how this could have happened. But the error still could not be explained due to the timing.

Not Working Computer: Office Access 2003 (11.8321.8405) SP3
Working Computer: Office Access 2003 (11.5614.5606)
So if you uninstalled and reinstalled, how come you have SP3?
 

Users who are viewing this thread

Back
Top Bottom