Access 2002 Db crashing due to one form element

[Siobhan Perricone]

I have a user who is having a problem with an access database that I
didn't build and haven't had anything to do with in the past.

The database opens up to the switchboard, and she clicks through to
the "look up by facility name" form, and opens it up. So far so good.
She is able to click on and view every single thing on this pretty
complicated form, including opening a variety of secondary forms.

However, whenever she clicks on the drop down menu to select a
facility to view in the form, Access crashes with nothing but the
"send this error to Microsoft?" error message. There is nothing to
give me a clue about what the real problem is.

She's not the only one who uses this database, but she is the only one
who has this problem. Everyone else can use the form just fine. She is
also the only person in her area with windows XP (all the rest have
Win2k). However, I am able to open the database on my computer and I
have no problem using the form to find a facility. I am also running
XP.

I've tried a compact and repair on the Db, but to no avail.

One thing that I think is a little odd is that the person who has
administrative rights to the Db has to log in when she runs it. It
presents here with a login dialog. But neither the woman having this
problem nor myself are presented with a login dialog when we open up
the Db. I don't *think* this would have anything to do with the actual
problem, but I'm not sure. So I just present this datapoint for
completeness.

I'm currently waiting to get administrative access to the form so I
can try making a copy of it and seeing if the copy works or not. Then
also trying to rebuild that single form element and see if that fixes
the problem for the woman.

However, if anyone has any other suggestions for where to poke to find
out what's cause this, I'd be very grateful to hear it.

--
Siobhan Perricone
Systems Developer
Vermont Agency of Natural Resources
(my comments are my own, not my employer's)

[david epsom dot com dot au]

> One thing that I think is a little odd is that the person who has

administrative rights to the Db has to log in when she runs it. It
presents here with a login dialog. But neither the woman having this
This is either because (a) she has a shortcut that takes her
to the administrative workgroup/username or (b) Because her
PC is set up to use the administrative workgroup (possibly
just by adding a password to the default login account).

After you get the Admin login UserName and PassWord, you can
try (b) Just change the password for 'admin' under security
in Access: if that fails (a) Get System.mdw from her PC:
if that fails (c) Check the WorkGroup Administrator on her
PC to see what workgroup file she is using.

(david)

"Siobhan Perricone" <si***************@nostatespam.vt.us> wrote in message
news:s6********************************@4ax.com... I have a user who is having a problem with an access database that I
didn't build and haven't had anything to do with in the past.

The database opens up to the switchboard, and she clicks through to
the "look up by facility name" form, and opens it up. So far so good.
She is able to click on and view every single thing on this pretty
complicated form, including opening a variety of secondary forms.

However, whenever she clicks on the drop down menu to select a
facility to view in the form, Access crashes with nothing but the
"send this error to Microsoft?" error message. There is nothing to
give me a clue about what the real problem is.

She's not the only one who uses this database, but she is the only one
who has this problem. Everyone else can use the form just fine. She is
also the only person in her area with windows XP (all the rest have
Win2k). However, I am able to open the database on my computer and I
have no problem using the form to find a facility. I am also running
XP.

I've tried a compact and repair on the Db, but to no avail.

One thing that I think is a little odd is that the person who has
administrative rights to the Db has to log in when she runs it. It
presents here with a login dialog. But neither the woman having this
problem nor myself are presented with a login dialog when we open up
the Db. I don't *think* this would have anything to do with the actual
problem, but I'm not sure. So I just present this datapoint for
completeness.

I'm currently waiting to get administrative access to the form so I
can try making a copy of it and seeing if the copy works or not. Then
also trying to rebuild that single form element and see if that fixes
the problem for the woman.

However, if anyone has any other suggestions for where to poke to find
out what's cause this, I'd be very grateful to hear it.

--
Siobhan Perricone
Systems Developer
Vermont Agency of Natural Resources
(my comments are my own, not my employer's)

[Janross]

Hi, Siobhan:

No great insights into this problem, but since no one else has really answered,
I thought I'd put in my two cents. If only one user is having the problem,
odds are the problem is with her machine. First place to check is references
(open up a module, click Tools/references) to see if any are marked missing.
If so, uncheck them; if not look at which ones are there and in which order,
and then compare to a machine using the same version of Access in which the
code does work.

Also, be sure you have all the same service releases on all the machines.

This is just standard stuff; no great ideas beyond that. Sorry.

HTH

Jan

I have a user who is having a problem with an access database that I
didn't build and haven't had anything to do with in the past.

The database opens up to the switchboard, and she clicks through to
the "look up by facility name" form, and opens it up. So far so good.
She is able to click on and view every single thing on this pretty
complicated form, including opening a variety of secondary forms.

However, whenever she clicks on the drop down menu to select a
facility to view in the form, Access crashes with nothing but the
"send this error to Microsoft?" error message. There is nothing to
give me a clue about what the real problem is.

She's not the only one who uses this database, but she is the only one
who has this problem. Everyone else can use the form just fine. She is
also the only person in her area with windows XP (all the rest have
Win2k). However, I am able to open the database on my computer and I
have no problem using the form to find a facility. I am also running
XP.

I've tried a compact and repair on the Db, but to no avail.

One thing that I think is a little odd is that the person who has
administrative rights to the Db has to log in when she runs it. It
presents here with a login dialog. But neither the woman having this
problem nor myself are presented with a login dialog when we open up
the Db. I don't *think* this would have anything to do with the actual
problem, but I'm not sure. So I just present this datapoint for
completeness.

I'm currently waiting to get administrative access to the form so I
can try making a copy of it and seeing if the copy works or not. Then
also trying to rebuild that single form element and see if that fixes
the problem for the woman.

However, if anyone has any other suggestions for where to poke to find
out what's cause this, I'd be very grateful to hear it.

--
Siobhan Perricone
Systems Developer
Vermont Agency of Natural Resources

Jan Stempel
Stempel Consulting

[Siobhan Perricone]

On 21 Apr 2004 14:24:12 GMT, ja*****@aol.com (Janross) wrote:

Hi, Siobhan:

No great insights into this problem, but since no one else has really answered,
I thought I'd put in my two cents. If only one user is having the problem,
odds are the problem is with her machine. First place to check is references
(open up a module, click Tools/references) to see if any are marked missing.
If so, uncheck them; if not look at which ones are there and in which order,
and then compare to a machine using the same version of Access in which the
code does work.

Also, be sure you have all the same service releases on all the machines.

This is just standard stuff; no great ideas beyond that. Sorry.

I managed to find the problem. I found an obscure reference to Access
2002 crashing with drop down menus that bookmark using Me. for their
reference rather than Forms![form1]. as their reference. We changed
the Me.s to Forms! and it completely fixed the problem.

I have a user who is having a problem with an access database that I
didn't build and haven't had anything to do with in the past.

The database opens up to the switchboard, and she clicks through to
the "look up by facility name" form, and opens it up. So far so good.
She is able to click on and view every single thing on this pretty
complicated form, including opening a variety of secondary forms.

However, whenever she clicks on the drop down menu to select a
facility to view in the form, Access crashes with nothing but the
"send this error to Microsoft?" error message. There is nothing to
give me a clue about what the real problem is.

She's not the only one who uses this database, but she is the only one
who has this problem. Everyone else can use the form just fine. She is
also the only person in her area with windows XP (all the rest have
Win2k). However, I am able to open the database on my computer and I
have no problem using the form to find a facility. I am also running
XP.

I've tried a compact and repair on the Db, but to no avail.

One thing that I think is a little odd is that the person who has
administrative rights to the Db has to log in when she runs it. It
presents here with a login dialog. But neither the woman having this
problem nor myself are presented with a login dialog when we open up
the Db. I don't *think* this would have anything to do with the actual
problem, but I'm not sure. So I just present this datapoint for
completeness.

I'm currently waiting to get administrative access to the form so I
can try making a copy of it and seeing if the copy works or not. Then
also trying to rebuild that single form element and see if that fixes
the problem for the woman.

However, if anyone has any other suggestions for where to poke to find
out what's cause this, I'd be very grateful to hear it.

--
Siobhan Perricone
Systems Developer
Vermont Agency of Natural Resources

Jan Stempel
Stempel Consulting

--
Siobhan Perricone
Systems Developer
Vermont Agency of Natural Resources
(my comments are my own, not my employer's)