Access/VBA irritants

[Bruce]

I recently 'upgraded' a number of our applications to Access 2003 from
Access 97. There are a few things I like about the newer (post 97)
versions of Access but they've also introduced a number of irritating
behaviors now that the distinction between what is 'Access' and what
is 'VBA' has been made more distinct. To wit:

Suppose I open Access 2003 and create a new module by clicking
Modules, New. This opens up a separate VBA window with Module1 in it,
a behavior which I suppose I can live with (especially since I have no
choice in the matter). Then suppose I create a few sub's and/or
functions in that new module. Now, suppose I accidentally close the
VBA window. It dutifully closes without prompting me to save my new
module. I know the code is out there somewhere because I can still
reference my new functions and sub's, but I don't see a way to get
back to edit it without attempting to close my Access project
altogether, at which point I am prompted to save my module. Even
then, I don't see how to get back to editing my new module without
saving it first. Even if I create another module (Module2 this time)
to force the VBA window to open, my first module does not appear in
the list of code windows. Where does it go? How can I get back to it
without following this torturous path?

Also, is there any way to get to VBA help from within the Access IDE
without first opening the code window?

What were they thinking?

Bruce

[Michael \(michka\) Kaplan [MS]]

Just hit Ctrl+G or Alt+F11 to get back to VBE.

There is no way to get the VBA topics from Access; you must be in the VBE to
get them.
--
MichKa [MS]
NLS Collation/Locale/Keyboard Development
Globalization Infrastructure and Font Technologies

This posting is provided "AS IS" with
no warranties, and confers no rights.
"Bruce" <br***@aristotle.net> wrote in message
news:d3**************************@posting.google.c om...

I recently 'upgraded' a number of our applications to Access 2003 from
Access 97. There are a few things I like about the newer (post 97)
versions of Access but they've also introduced a number of irritating
behaviors now that the distinction between what is 'Access' and what
is 'VBA' has been made more distinct. To wit:

Suppose I open Access 2003 and create a new module by clicking
Modules, New. This opens up a separate VBA window with Module1 in it,
a behavior which I suppose I can live with (especially since I have no
choice in the matter). Then suppose I create a few sub's and/or
functions in that new module. Now, suppose I accidentally close the
VBA window. It dutifully closes without prompting me to save my new
module. I know the code is out there somewhere because I can still
reference my new functions and sub's, but I don't see a way to get
back to edit it without attempting to close my Access project
altogether, at which point I am prompted to save my module. Even
then, I don't see how to get back to editing my new module without
saving it first. Even if I create another module (Module2 this time)
to force the VBA window to open, my first module does not appear in
the list of code windows. Where does it go? How can I get back to it
without following this torturous path?

Also, is there any way to get to VBA help from within the Access IDE
without first opening the code window?

What were they thinking?

Bruce

[XMVP]

Try using the Save icon. This is a little brown thing on the toolbar that
looks like a floppy diskette, which is a kind of removable media.
"Bruce" <br***@aristotle.net> wrote in message
news:d3**************************@posting.google.c om...

I recently 'upgraded' a number of our applications to Access 2003 from
Access 97. There are a few things I like about the newer (post 97)
versions of Access but they've also introduced a number of irritating
behaviors now that the distinction between what is 'Access' and what
is 'VBA' has been made more distinct. To wit:

Suppose I open Access 2003 and create a new module by clicking
Modules, New. This opens up a separate VBA window with Module1 in it,
a behavior which I suppose I can live with (especially since I have no
choice in the matter). Then suppose I create a few sub's and/or
functions in that new module. Now, suppose I accidentally close the
VBA window. It dutifully closes without prompting me to save my new
module. I know the code is out there somewhere because I can still
reference my new functions and sub's, but I don't see a way to get
back to edit it without attempting to close my Access project
altogether, at which point I am prompted to save my module. Even
then, I don't see how to get back to editing my new module without
saving it first. Even if I create another module (Module2 this time)
to force the VBA window to open, my first module does not appear in
the list of code windows. Where does it go? How can I get back to it
without following this torturous path?

Also, is there any way to get to VBA help from within the Access IDE
without first opening the code window?

What were they thinking?

Bruce

[Larry Linson]

"XMVP" <ac***********@hotmail.com> wrote in message
news:te********************@vnet-inc.com...

Interesting that you should go back to using such an appropriate e-mail
handle again, Don. Did even the anonymizers finally get fed up with you?