Solved Access not displaying properly

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

 

[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

 

[AHeyne]

@isladogs : If you could make a snapshot of your VM you could easily check if Access 2003 still works properly after upgrading to SP3 or also to 11.8321.8405.
That would at least end this long thread with a conclusion, I think. ;-)

 

[Gasman]

The O/P could even do the same and see if it behaves in a VM?, but if they are not even comfortable re/installing windows, that is not likely an option?

 

[isladogs]

@AHeyne
Whilst I could do that, I'm using a different OS for that VM so I don't think it would prove anything
After almost 180 posts at the two forums, the OP needs to bite the bullet and take the necessary action - install a fresh copy or upgrade

 

[Gasman]

Well they have a workaround, so they can use that.

 

[AHeyne]

@AHeyne
...I'm using a different OS for that VM so I don't think it would prove anything

Ah, ok, you're right.

 

[The_Doc_Man]

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/

It is less that the super moderator does or doesn't want the thread to continue. It is that getting information from you and getting you to respond to suggestions with a report on results seems unusually difficult, which raises frustration level. We are all glad to help but usually get more evidence of active cooperation. Not saying you DIDN'T cooperate, but we didn't see strong evidence of that cooperation. When problem threads reach a post count greater than 100, that is never a good sign for ANYONE involved in the problem. I won't say this is insoluble, but it may EFFECTIVELY be that way.

 

[Gasman]

Continuing on the other site where post count is only up to #56

 

[AccessShell]

I removed McAfee. The DBs now open properly. I really don't know hoe McAfee messed thing up.
I had been on another forum trying to learn about Anti-Virus apps to use. They suggested I delete McAfee and let Windows Security take over.

 

[The_Doc_Man]

Probably that means that McAfee had downgraded its "opinion" of Access, which in turn probably means it could have been fixed by going into McAfee to make Access fully trusted. Since I don't have McAfee I don't know the exact method to tell it to trust a particular program, but I had a similar problem for a different utility program with Kaspersky and changing its trust level was my solution. DIdn't think of that in your context, I guess because the AV package didn't come up in the thread. Glad you found out - and thanks for publishing your answer. Others who search for DB startup-display problems might learn something very useful.

 

[GPGeorge]

Probably that means that McAfee had downgraded its "opinion" of Access, which in turn probably means it could have been fixed by going into McAfee to make Access fully trusted. Since I don't have McAfee I don't know the exact method to tell it to trust a particular program, but I had a similar problem for a different utility program with Kaspersky and changing its trust level was my solution. DIdn't think of that in your context, I guess because the AV package didn't come up in the thread. Glad you found out - and thanks for publishing your answer. Others who search for DB startup-display problems might learn something very useful.

IIRC, many AV applications, like Norton or McAfee. have "white list" or "black list" options for various programs, which usually means Access needs to called out in those cases.

 

[Deleted member 147267]

My post (36), March 27 at AccessForums.net:

Found another possibility - AV. Perhaps the "good" pc has none, or a different version, or a different setting. I don't know (or forgot) what environment you're working in, so AV might not apply. AV should not be scanning mdb files if that is the case.

OP posted 11 more times there before disabling AV. So yeah to post 126 here.

 

[Gasman]

My post (36), March 27 at AccessForums.net:

OP posted 11 more times there before disabling AV. So yeah to post 126 here.

Hey @Micron,
Welcome back.

 

[Deleted member 147267]

Not back, really. Just wanted to confirm what was said over yonder; 'specially because it turned out to be the cause. By my reckoning, you guys kept at it for 10 or 11 more days after that. It seems like an unfortunate waste of people's time. I only followed here because I wanted to be sure I was in on the solution since nothing over yonder seemed to solve it.