form won't open

[gthomson]

Using Access 2003 and have a problem with a form that won't open in
either form or design view.

Details: The database is split into back and front end. Each user of
the db has a separate copy of the front end. One of my users can't open
the main form though she can open all the other forms. I deleted her
copy of the fe, and gave her a new copy. Same problem. No one else has
this issue.

I'm at a loss. Does anyone have any ideas?


Thanks,
gt

 

[Allen Browne]

That's odd. Replacing the front end was a good idea in case she had a
corrupted form, but that did not solve it.

Are you running Access security? Any possibility this user does not have
permission for something the form refers to?

Does this machine have a problem with references? Press Ctrl+G to open the
immediate window, and choose References from the Tools menu. Anything marked
"MISSING"? More on references:
http://allenbrowne.com/ser-38.html

Is there any code in the Open event of this form, or its Load or Current
events? Anything that could block it being shown?

Does it open directly from the Database window (as distinct from using the
OpenForm action/method)?

Any Timer events running that could interfere?

Any difference in the file versions on this machine compared to the others?
Particularly:
msjet40.dll
msaccess.exe

 

[gthomson]

Allen:

Thanks for the response. Here's some more data. We refreshed her
profile and it worked - once. The next time she tried to open it, back
to the same old problem. I managed to coax out an error msg: 2501 The
Open Form action was cancelled.

Additional responses interspersed.

That's odd. Replacing the front end was a good idea in case she had a

corrupted form, but that did not solve it.

Are you running Access security? Any possibility this user does not have
permission for something the form refers to?

I wondered about security, but she can open all the other forms in the
same db, and there's no special security set on the "stubborn" form.
Besides she has been using this application for months with no
problems.

Does this machine have a problem with references? Press Ctrl+G to open the
immediate window, and choose References from the Tools menu. Anything marked
"MISSING"? More on references:
http://allenbrowne.com/ser-38.html

References were my first idea, but they're OK. Also if I log into her
machine with my profile, I have no problem with the form.

Is there any code in the Open event of this form, or its Load or Current
events? Anything that could block it being shown?

There is code in the Open, Load, and Current - though for the life of
me I can't see how those lines of code could block the form from
opening. I guess I could try commenting it all out.

Does it open directly from the Database window (as distinct from using the
OpenForm action/method)?

Can't open it via code, or from the database window in either form or
design view.

Any Timer events running that could interfere?

Not that I know of.

Any difference in the file versions on this machine compared to the others?
Particularly:
msjet40.dll
msaccess.exe

I hadn't thought of that, but figured since she's been using the app
for months with no issues, that the problem was elsewhere.

 

[Allen Browne]

The most troubing thing aspect of your reply is that you cannot open this
form in *design* view directly from from the database window on that
machine.

None of the code runs when you open in design view, so it cannot be the
events. Neither does it attempt to load the form or its
combos/listboxes/subforms if you open directly into design view. I doubt you
would receive error 2501 in this case either: is there a different error?

If you are using Access security (mdw file), it is still possible that
something has gone wrong with the permissions.

Definately worth checking the file versions for msaccess.exe, msjet40.dll
and any libraries that are referenced (Tools | References, from a code
window.)

It might also be worth trying to export the form to a text file from her
machine, doing the same from another machine and seeing if the results are
identical. The (undocumented) command is something like this:
SaveAsText acForm, "Form1", "C:\form1.txt"
Then use a utility such as FC at the command prompt to compare the two
copies from the two machines. If they are identical, the form is not
corrupt, so the issue has to be with permissions or the installation of
Access.

HTH to track it down.

 

[gthomson]

The most troubing thing aspect of your reply is that you cannot open this
form in *design* view directly from from the database window on that
machine.

Yeah, pretty odd.

None of the code runs when you open in design view, so it cannot be the
events. Neither does it attempt to load the form or its
combos/listboxes/subforms if you open directly into design view. I doubt you
would receive error 2501 in this case either: is there a different

error?

No error - nothing at all. Right clicking and choosing Open in Design
View does nothing, nada, zip.

If you are using Access security (mdw file), it is still possible that
something has gone wrong with the permissions.

Nope, no mdw file. But there's something screwy going on because if I
log into her machine, I can open the form with no problem. Yesterday we
refreshed her XP profile (deleted it, and then let windows create it
afresh). After that she could log in and open the form. Once. After
that one time it was back to the old misbehavior. But why would her
profile affect just one form in this one database and in this
particular way? She has no problems with any other databases she uses.

Definately worth checking the file versions for msaccess.exe, msjet40.dll
and any libraries that are referenced (Tools | References, from a code
window.)

That will be my next step.

It might also be worth trying to export the form to a text file from her
machine, doing the same from another machine and seeing if the results are
identical. The (undocumented) command is something like this:
SaveAsText acForm, "Form1", "C:\form1.txt"
Then use a utility such as FC at the command prompt to compare the two
copies from the two machines. If they are identical, the form is not
corrupt, so the issue has to be with permissions or the installation of
Access.

That's a great idea. I'll do that, too. Thanks for your continued help;
I really appreciate it.