Re: Microsoft Cleanliness

To go to a code window,
I would press Ctrl+F6 to go to the next window, and keep looping
through the form and report and code windows until I got to the
one I wanted.

That works in A97, too.

No, I was talking about A97. I'm saying, in A97, I'd have to use Ctrl+F6 to
loop through the open windows until got to my code window. I'm saying it was
a pain.


With the
separate VBE, the code window I'm working in is always on top. It
also allows me to toggle to the app while the code is paused and
look at it.

How the window *not* on top in A97?

When you open other things after you open the code window, the window's not
on top anymore. Sure, you could click the code toolbar button; but that
requires grabbing the mouse. So, in A97, the code window that you're working
in gets pushed back in the set, whereas with the standalone VBE, it's always
on top. Granted if I open another code window it won't be on top anymore.
But at least it won't get pushed back just by opening another form or
report.



I realize that you probably didn't work with the windows
maximized, and that created another problem: having a smaller work
area for your forms, reports, and code. So it's a lose-lose
situation, IMO.

I like switching back and forth between maximized and not. Because
of all the extra stuff in the VBE (which is basically required to
navigate), it's really inefficient to *not* work with the code
window maximized.

Well, I always work maximized because I like the extra room. So there we
have it: A97 works better with non-maximized windows, and A2000+ works
better with maximized windows. That's why we each prefer a different
version, because we don't both work with maximized windows exclusively.


With the separate code window I
can just toggle back and forth between the current form/report
and it's code with a simple Alt+Tab. Sweet.

What's so hard about opening the module and the form and using
Ctrl-F6 and Shit-Ctrl-F6?

As noted above, I would use Ctrl+F6. But when you have several
forms and reports open and several code modules, it's a lot of
looping just to get back to what you want. Much simpler just to
press Alt+Tab to go back and forth between the currently-worked on
form and it's code.

This has not been a problem for me in A97. What you say about
Alt-Tab doesn't always work, because it depends on what windows you
have open and which one last had the focus. If you have multiple
instances of Access and the VBE, then you are back to the exact same
TaskBar problem as before.

Well, that's true. But I'm usually only working in one VBE at at a time. So,
I may have multiple instances of Access open, but when I press Alt+Tab I can
easily see the icon on the VBE, and it's easy to go to my code. With Ctrl+F6
there is no such visual indicator, and I have to just keep looping through
windows until I get to the one I want.

And there's no way to change the order. So if my code window is 3 windows
back from my form, I have always loop back three. But with the VBE, when I
go to a code window, it stays on top of the VBE, and it's right there when I
Alt+Tab to it again.



Or placing them so that they don't overlap
and you can click on the title bar of either the form or the
module to bring it forward?

Not following you here.

Well, if you work maximized, it won't work. If you don't work
maximized it's quite easy to navigate. In the VBE, it's pretty much
impossible to work non-maximized since there's so much other junk in
the window that can't be efficiently closed.


I see what you're saying here. You're talking about non-maximized windows
and clicking on the title bar. Right, that's nice. But then you lose all
that coding space. Or you have to keep double-clicking the title bar to go
back and from between maximized and non-maximized. I prefer to just keep it
maximized and not have to deal with those extra steps.

But, at least we figured out why we're each so vehement about our particular
preferred version.

Neil





--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/


.

Relevant Pages

  • Re: first attempt at a report - HELP!
    ... Select the Modules tab in the Database window, ... Paste the code below into the Code window, ... Create a new query containing both tblDate and your other table. ... >> Now to use the query in the report. ...
    (microsoft.public.access.reports)
  • Re: Open Word in a specific folder
    ... work in a code editting window. ... Microsoft Visual FoxPro MVP ... In a code Window: ...
    (microsoft.public.fox.programmer.exchange)
  • Re: Open Word in a specific folder
    ... I would I use the Code Window Syntax?? ... Microsoft Visual FoxPro MVP ...
    (microsoft.public.fox.programmer.exchange)
  • Re: VBA Editor Window(s) size challenge
    ... Deleting the key will delete any changes you've made to the layout of the VBE. ... Resize your Immediate Window AFTER it is docked. ... Bring up your last window (Code window in my case - Upper Right) and maximize it. ... If I closed the Immediate Window the Code Window would resize. ...
    (microsoft.public.excel.programming)
  • Re: Subform
    ... a code window), and see if it is expecting something that is not present. ... Press Ctrl+G to open the Immediate window. ... LinkMasterFields property setting has produced this error: ... and autonumber field type and in the Child Field it is a number ...
    (microsoft.public.access.forms)