Access 2003 - problems with right mouse button

[Abay]

Hello,

I have two different Access 2003 databases, one has a problem with showing
options when the right mouse button is clicked on a table, query or
anything, the other one does not.

This started happening out of the blue ... I checked tools, options thinking
I had inadvertly set some sort of option, but there is nothing that I can
see that would affect the mouse in one data base and not the other .. very
strange. It is the same on my computer at home and at the office ...

Any help on this would be much appreciated.

Abay

 

[Allen Browne]

Is there anything else running that could interfere?

The Timer event of a form, for example?

 

[Abay]

Many thanks for your reply Allen .. I can't see that anything else is
running, but have to confess that I do not know what "The timer even of a
form" is .. please excuse my ignorance

Abay

 

[Allen Browne]

To learn about the timer event that can interfere with all sorts of things:

1. Open a form in design view.
2. Open the Properties box (View menu.)
3. Looking at the properties of the form (not of a text box), there's an On
Timer property that specifies a macro or [Event Procedure] that should run
each time the form's timer fires, and a Timer Interval property that
specifies how frequently (in milliseconds.)

If that doesn't apply to your situation, what setting do you have under:
Tools | Startup | Allow Default Shortcut Menus

If that doesn't help either, you may need to decompile, compact, and get
Access to create a new database. Post back if you would like details for
this.

 

[Abay]

thanks again for your help .. will give it a try ..

Abay

To learn about the timer event that can interfere with all sorts of
things:

1. Open a form in design view.
2. Open the Properties box (View menu.)
3. Looking at the properties of the form (not of a text box), there's an
On Timer property that specifies a macro or [Event Procedure] that should
run each time the form's timer fires, and a Timer Interval property that
specifies how frequently (in milliseconds.)

If that doesn't apply to your situation, what setting do you have under:
Tools | Startup | Allow Default Shortcut Menus

If that doesn't help either, you may need to decompile, compact, and get
Access to create a new database. Post back if you would like details for
this.

--
Allen Browne - Microsoft MVP. Perth, Western Australia

Reply to group, rather than allenbrowne at mvps dot org.

Many thanks for your reply Allen .. I can't see that anything else is
running, but have to confess that I do not know what "The timer even of a
form" is .. please excuse my ignorance

Abay

 

[Abay]

Nothing is set re: the Timer property. Tool,start-up,allow default full
menus is set .. changed it to "allow default short menus" to no effect, my
preference is full menus. Have compacted the dbase, but not sure what you
meant to get Access to create a new dbase .. do you mean to create an empty
one and then import the tables from the problem dbase?

Thanks again for your help

Abay

thanks again for your help .. will give it a try ..

Abay

To learn about the timer event that can interfere with all sorts of
things:

1. Open a form in design view.
2. Open the Properties box (View menu.)
3. Looking at the properties of the form (not of a text box), there's an
On Timer property that specifies a macro or [Event Procedure] that should
run each time the form's timer fires, and a Timer Interval property that
specifies how frequently (in milliseconds.)

If that doesn't apply to your situation, what setting do you have under:
Tools | Startup | Allow Default Shortcut Menus

If that doesn't help either, you may need to decompile, compact, and get
Access to create a new database. Post back if you would like details for
this.

--
Allen Browne - Microsoft MVP. Perth, Western Australia

Reply to group, rather than allenbrowne at mvps dot org.

Many thanks for your reply Allen .. I can't see that anything else is
running, but have to confess that I do not know what "The timer even of
a form" is .. please excuse my ignorance

Abay
Is there anything else running that could interfere?

The Timer event of a form, for example?

--
Allen Browne - Microsoft MVP. Perth, Western Australia

Reply to group, rather than allenbrowne at mvps dot org.


I have two different Access 2003 databases, one has a problem with
showing options when the right mouse button is clicked on a table,
query or anything, the other one does not.

This started happening out of the blue ... I checked tools, options
thinking I had inadvertly set some sort of option, but there is
nothing that I can see that would affect the mouse in one data base
and not the other .. very strange. It is the same on my computer at
home and at the office ...

Any help on this would be much appreciated.

Abay

 

[Allen Browne]

Yes. Decompile first, and then get Access to recreate everything for you.

Here's the standard sequence. Follow in order:

1. Uncheck the boxes under:
Tools | Options | General | Name AutoCorrect
Explanation of why:
http://allenbrowne.com/bug-03.html

2. Compact the database to get rid of this junk:
Tools | Database Utilities | Compact/Repair

3. Close Access. Make a backup copy of the file. Decompile the database by
entering something like this at the command prompt while Access is not
running. It is all one line, and include the quotes:
"c:\Program Files\Microsoft office\office\msaccess.exe" /decompile
"c:\MyPath\MyDatabase.mdb"

4. Open Access (holding down the Shift key if you have any startup code),
and compact again.

5. Create a new (blank) database.
First thing, make sure Name AutoCorrect is off (as 1 above.)

6. Import everything from the old database:
File | Get External

7. Open a code window.
Choose References from the Tools menu.
Uncheck any references you do not need.
For a list of the ones you typically need in your version of Access, see:
http://allenbrowne.com/ser-38.html

8. Still in the code window, choose Compile from the Debug menu.
Fix any errors, and repeat until it compiles okay.

At this point, you should have a database where the name-autocorrect errors
are gone, the indexes are repaired, inconsistencies between the text- and
compiled-versions of the code are fixed, reference ambiguities are resolved,
and the code syntax is compilable.

If it is still a problem, the next step would be to make a new copy, and
import only half the stuff. By handling half, then half of that half, you
can whittle it down until you pin down the culprit.

--
Allen Browne - Microsoft MVP. Perth, Western Australia

Reply to group, rather than allenbrowne at mvps dot org.

Nothing is set re: the Timer property. Tool,start-up,allow default full
menus is set .. changed it to "allow default short menus" to no effect, my
preference is full menus. Have compacted the dbase, but not sure what you
meant to get Access to create a new dbase .. do you mean to create an
empty one and then import the tables from the problem dbase?

Thanks again for your help

Abay

thanks again for your help .. will give it a try ..

Abay

To learn about the timer event that can interfere with all sorts of
things:

1. Open a form in design view.
2. Open the Properties box (View menu.)
3. Looking at the properties of the form (not of a text box), there's an
On Timer property that specifies a macro or [Event Procedure] that
should run each time the form's timer fires, and a Timer Interval
property that specifies how frequently (in milliseconds.)

If that doesn't apply to your situation, what setting do you have under:
Tools | Startup | Allow Default Shortcut Menus

If that doesn't help either, you may need to decompile, compact, and get
Access to create a new database. Post back if you would like details for
this.

Many thanks for your reply Allen .. I can't see that anything else is
running, but have to confess that I do not know what "The timer even of
a form" is .. please excuse my ignorance

Abay
Is there anything else running that could interfere?

The Timer event of a form, for example?


I have two different Access 2003 databases, one has a problem with
showing options when the right mouse button is clicked on a table,
query or anything, the other one does not.

This started happening out of the blue ... I checked tools, options
thinking I had inadvertly set some sort of option, but there is
nothing that I can see that would affect the mouse in one data base
and not the other .. very strange. It is the same on my computer at
home and at the office ...

 

[Abay]

Many thanks again Allen .. this looks like quite a job, so will do it when I
have the time to concentrate on it, tomorrow evening .. will get back then

Abay

Yes. Decompile first, and then get Access to recreate everything for you.

Here's the standard sequence. Follow in order:

1. Uncheck the boxes under:
Tools | Options | General | Name AutoCorrect
Explanation of why:
http://allenbrowne.com/bug-03.html

2. Compact the database to get rid of this junk:
Tools | Database Utilities | Compact/Repair

3. Close Access. Make a backup copy of the file. Decompile the database by
entering something like this at the command prompt while Access is not
running. It is all one line, and include the quotes:
"c:\Program Files\Microsoft office\office\msaccess.exe" /decompile
"c:\MyPath\MyDatabase.mdb"

4. Open Access (holding down the Shift key if you have any startup code),
and compact again.

5. Create a new (blank) database.
First thing, make sure Name AutoCorrect is off (as 1 above.)

6. Import everything from the old database:
File | Get External

7. Open a code window.
Choose References from the Tools menu.
Uncheck any references you do not need.
For a list of the ones you typically need in your version of Access, see:
http://allenbrowne.com/ser-38.html

8. Still in the code window, choose Compile from the Debug menu.
Fix any errors, and repeat until it compiles okay.

At this point, you should have a database where the name-autocorrect
errors are gone, the indexes are repaired, inconsistencies between the
text- and compiled-versions of the code are fixed, reference ambiguities
are resolved, and the code syntax is compilable.

If it is still a problem, the next step would be to make a new copy, and
import only half the stuff. By handling half, then half of that half, you
can whittle it down until you pin down the culprit.

--
Allen Browne - Microsoft MVP. Perth, Western Australia

Reply to group, rather than allenbrowne at mvps dot org.

Nothing is set re: the Timer property. Tool,start-up,allow default full
menus is set .. changed it to "allow default short menus" to no effect,
my preference is full menus. Have compacted the dbase, but not sure what
you meant to get Access to create a new dbase .. do you mean to create an
empty one and then import the tables from the problem dbase?

Thanks again for your help

Abay

thanks again for your help .. will give it a try ..

Abay

To learn about the timer event that can interfere with all sorts of
things:

1. Open a form in design view.
2. Open the Properties box (View menu.)
3. Looking at the properties of the form (not of a text box), there's
an On Timer property that specifies a macro or [Event Procedure] that
should run each time the form's timer fires, and a Timer Interval
property that specifies how frequently (in milliseconds.)

If that doesn't apply to your situation, what setting do you have
under:
Tools | Startup | Allow Default Shortcut Menus

If that doesn't help either, you may need to decompile, compact, and
get Access to create a new database. Post back if you would like
details for this.

Many thanks for your reply Allen .. I can't see that anything else is
running, but have to confess that I do not know what "The timer even
of a form" is .. please excuse my ignorance

Abay
Is there anything else running that could interfere?

The Timer event of a form, for example?


I have two different Access 2003 databases, one has a problem with
showing options when the right mouse button is clicked on a table,
query or anything, the other one does not.

This started happening out of the blue ... I checked tools, options
thinking I had inadvertly set some sort of option, but there is
nothing that I can see that would affect the mouse in one data base
and not the other .. very strange. It is the same on my computer at
home and at the office ...

 

[Abay]

Hello Allen,

Apologies for not getting back sooner .. I have not been able get back to my
access problem before now .. I found I had to create a new d'base and import
bit by bit (as you suggested) from the old one. I did not need all that was
there, and so do not know exactly what caused the problem as I only imported
what I needed and now I can use right mouse button to cut and paste etc. to
my heart's content so to speak.

Many thanks for your help, it is so much appreciated.

Abay

Yes. Decompile first, and then get Access to recreate everything for you.

Here's the standard sequence. Follow in order:

1. Uncheck the boxes under:
Tools | Options | General | Name AutoCorrect
Explanation of why:
http://allenbrowne.com/bug-03.html

2. Compact the database to get rid of this junk:
Tools | Database Utilities | Compact/Repair

3. Close Access. Make a backup copy of the file. Decompile the database by
entering something like this at the command prompt while Access is not
running. It is all one line, and include the quotes:
"c:\Program Files\Microsoft office\office\msaccess.exe" /decompile
"c:\MyPath\MyDatabase.mdb"

4. Open Access (holding down the Shift key if you have any startup code),
and compact again.

5. Create a new (blank) database.
First thing, make sure Name AutoCorrect is off (as 1 above.)

6. Import everything from the old database:
File | Get External

7. Open a code window.
Choose References from the Tools menu.
Uncheck any references you do not need.
For a list of the ones you typically need in your version of Access, see:
http://allenbrowne.com/ser-38.html

8. Still in the code window, choose Compile from the Debug menu.
Fix any errors, and repeat until it compiles okay.

At this point, you should have a database where the name-autocorrect
errors are gone, the indexes are repaired, inconsistencies between the
text- and compiled-versions of the code are fixed, reference ambiguities
are resolved, and the code syntax is compilable.

If it is still a problem, the next step would be to make a new copy, and
import only half the stuff. By handling half, then half of that half, you
can whittle it down until you pin down the culprit.

--
Allen Browne - Microsoft MVP. Perth, Western Australia

Reply to group, rather than allenbrowne at mvps dot org.

Nothing is set re: the Timer property. Tool,start-up,allow default full
menus is set .. changed it to "allow default short menus" to no effect,
my preference is full menus. Have compacted the dbase, but not sure what
you meant to get Access to create a new dbase .. do you mean to create an
empty one and then import the tables from the problem dbase?

Thanks again for your help

Abay

thanks again for your help .. will give it a try ..

Abay

To learn about the timer event that can interfere with all sorts of
things:

1. Open a form in design view.
2. Open the Properties box (View menu.)
3. Looking at the properties of the form (not of a text box), there's
an On Timer property that specifies a macro or [Event Procedure] that
should run each time the form's timer fires, and a Timer Interval
property that specifies how frequently (in milliseconds.)

If that doesn't apply to your situation, what setting do you have
under:
Tools | Startup | Allow Default Shortcut Menus

If that doesn't help either, you may need to decompile, compact, and
get Access to create a new database. Post back if you would like
details for this.

Many thanks for your reply Allen .. I can't see that anything else is
running, but have to confess that I do not know what "The timer even
of a form" is .. please excuse my ignorance

Abay
Is there anything else running that could interfere?

The Timer event of a form, for example?


I have two different Access 2003 databases, one has a problem with
showing options when the right mouse button is clicked on a table,
query or anything, the other one does not.

This started happening out of the blue ... I checked tools, options
thinking I had inadvertly set some sort of option, but there is
nothing that I can see that would affect the mouse in one data base
and not the other .. very strange. It is the same on my computer at
home and at the office ...

 

[Allen Browne]

Good news! Thanks for sharing the outcome.