yeah; I bitched up a storm about this
I find it even more humorous
if you programmatically use a 2nd instance of Access; and you set this
2nd instance to be 'not visible'
even when you close the 1st instance; the 2nd instance still has a
stupid looking property box
seems like a security hole to me; I mean-- using Access
programmatically and making it invisible-- it should be invivisble
but when i close the 1st app that damn properties window from the 2nd
instance is VISIBLE
I tried bitching up a storm about this VERY SAME BUG-- THAT YOU
MENTION-- WHEN I WORKED AT MICROSOFT
SERIOUSLY
those dipshits would rather fire someone with an IQ of 180 than fix a
silly focus bug
-Aaron
On Mar 29, 3:02 pm, "'69 Camaro" <ForwardZERO_SPAM.To.
69Cam...@Spameater.orgZERO_SPAM> wrote:
> Hi, Vlado.
>
> > Are there any workarounds?
>
> a.) Click a few more times while going back and forth from the Access
> window and VB Editor until the window you want shows up.
>
> b.) The toolbars change their order and appear/disappear depending upon
> what the active object is and what view it is in.
>
> c.) Use Access 97 online help.
>
> > Was there any public beta testing or MVP testing?
>
> Yes.
>
> > What do you think: Will MS release a new SP for A2002?
>
> Nope. Perhaps you should move on to a newer version of Access that is
> scheduled for future service pack releases or move to another development
> environment that you don't hate. There's not much to hate about Borland's
> Turbo C if you want my opinion, but it's designed for coders, not RAD
> software developers.
>
> HTH.
> Gunny
>
> Seehttp://www.QBuilt.comfor all your database needs.
> Seehttp://www.Access.QBuilt.comfor Microsoft Access tips and tutorials.
> Blogs:http://www.DataDevilDog.BlogSpot.com...utors2.htmlfor contact
> info.
>
> "Vladimír Cvajniga" <nos...@thank.you> wrote in message
>
> news:(E-Mail Removed)...
>
>
>
> > #1
>
> > 1) I set the breakpoint in a A2002 code.
> > 2) I open and maximize a form and then run the code.
> > 3) Debugger stops the execution at the breakpoint.
> > 4) I stop the code execution.
> > 5) I switch from code to design environment (to check form properties).
>
> > I'd expect that The Form will be on the top of all open forms. Instead,
> > there's a DB window (form's list) on the top.
> > ----------------------------
> > #2
>
> > 1) I set the breakpoint in a A2002 code.
> > 2) I open a form in design mode and open Properties window.
> > 3) I switch to form view, maximize a form and then run the code.
> > 4) Debugger stops the execution at the breakpoint.
> > 5) I stop the code execution.
> > 6) I want to switch from code to design environment (to check form
> > properties) by clicking the taskbar window.
>
> > I'd expect that The Form will be on the top of all open forms. Instead,
> > only form's Properties window pops up and I have to close it if I want to
> > get back to a form view.
> > ----------------------------
> > #3
>
> > When I go to form/report design view my toolbars very often change their
> > order without any known reason. The same in A97.
> > ----------------------------
> > #4, 5, 6, ...
> > Too many help bugs...
> > ----------------------------
> > There are other bugs as well, see some of my previous posts.
> > I REALLY HATE #1, #2 and #3! And I hate A2002 help! Worst help ever
> > seen... :-(
> > Are there any workarounds?
>
> > It seems that MS guys & gals didn't test A2002 before it was on the
> > stock... Was there any public beta testing or MVP testing?
>
> > What do you think: Will MS release a new SP for A2002?
>
> > TIA
>
> > Vlado- Hide quoted text -
>
> - Show quoted text -