Solved Access not displaying properly

[AccessShell]

The catalogs listed by Ahayne are dated 2012 and 2022. The DBs stopped opening correctly about 2 months ago.

 

[CJ_London]

Why don’t you upload a ‘ not working’ db to the forum - we can see if opening in a later version provides any clues

 

[AccessShell]

OK, I will do it, but I already said that on the other WIN10 computer, it works just fine.

 

[AccessShell]

Look in Post #28. I already uploaded a DB

 

[AHeyne]

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.

 

[Gasman]

Someone with A2003 will need to open the database to let us know what he sees.

Colin has already done that. It is the O/P's PC that is at fault.

 

[AHeyne]

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:

 

[AccessShell]

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)

 

[AHeyne]

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.

 

[The_Doc_Man]

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" happens."

 

[Pat Hartman]

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)

I pointed this out a hundred posts ago!!!! But you never looked.

 

[Gasman]

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?

 

[AccessShell]

It does not make sense.
First of all, I did not uninstall, I just re-installed. I don't know if that is different.
Second, The error started to happen at least one month before I asked for help
Curious, if A203 is no longer supported, why the updates listed in a previous post.

 

[Gasman]

It is.

 

[AHeyne]

So if you uninstalled and reinstalled, how come you have SP3?

Build 11.8321.8405 is even newer than SP3. It represents the latest version known to me.

Interesting would be now, which build @isladogs has, because on his pc it is running well he wrote in #34.

 

[AccessShell]

Look, all I know is I ran the program to re-install Office Pro 2003. It came back with "Successful".

 

[Pat Hartman]

And we're at 116 posts here and who knows how many elsewhere. You know the problem - the Windows version. And here we are?????

 

[isladogs]

I’m away from my PC for a few hours but I do remember 2003 SP3 had a major bug and a hotfix was released to fix that.
I would suggest uninstalling 2003 completely and reinstalling again. If that fails then look at Windows or upgrade Office

 

[AccessShell]

Well, it seems the super moderator does not this thread to continue. I cannot flag this as "solved". So, I will flag this as "unwatched" and respond to anymore posts.

For those of you, that tried to help, I am grateful.

Going offline now/

 

[isladogs]

FWIW I have A2003 build 11.5614.5606. Its on a VM for very occasional use so I never bothered to installed the various service packs
I doubt that SP3 is the issue for the OP however. More likely to be a Windows update as already stated