Results 1 to 10 of 10
  1. #1
    Join Date
    Sep 2008
    Location
    NM, USA
    Posts
    97

    Question Unanswered: Program isn't observing break points

    All I did was edit the message string that is supposed to show up in a pop-up prompt, and now clicking Enter on the form doesn't do anything.

    I put break points after the form load subroutine, and after several points in the btnEnter_click() subroutine, and nothing is happening. The program doesn't break at any of the indicated points.

    Has anyone encountered this problem in Microsoft Access before? Is my program bugged, or is the MS Access application its self bugged? Any suggestions would be helpful.

    Thanks.

    EDIT:
    I removed the changes I made to the class module that issues the prompt (I changed the message string back to what it was before), but the program still isn't observing any breakpoints, in any of my form modules or class modules, anywhere. It isn't observing my Debug.Print commands either. If I put in a Debug.Print [whatever variable], the program won't do anything; it's like you're just clicking empty buttons.

    I am very perplexed.
    Last edited by atsukoarai86; 10-15-09 at 14:17.
    "Unix is user friendly... It's just very picky about its friends."

    The best things in life...are well-documented.

  2. #2
    Join Date
    May 2005
    Posts
    1,191
    Have you compiled your code recently? Do you have error handling in this routing (like "On Error Resume Next" or something)?
    Me.Geek = True

  3. #3
    Join Date
    Sep 2008
    Location
    NM, USA
    Posts
    97
    Quote Originally Posted by nckdryr
    Have you compiled your code recently? Do you have error handling in this routing (like "On Error Resume Next" or something)?
    Yes, I tried recompiling the the program, but that didn't do a thing... it is still ignoring the break points and On Error statements. It's like the program isn't doing anything at all when I click "Enter" on the form. It isn't executing any code, it seems.

    /frustration
    "Unix is user friendly... It's just very picky about its friends."

    The best things in life...are well-documented.

  4. #4
    Join Date
    Sep 2008
    Location
    NM, USA
    Posts
    97

    Gragh

    God.. Now it's printing the Debug statements, but it still isn't BREAKING at the break points.

    ...why does it seem like my program has become sentient and is doing thing at random to me.
    "Unix is user friendly... It's just very picky about its friends."

    The best things in life...are well-documented.

  5. #5
    Join Date
    Aug 2009
    Location
    Up Nort' Wi
    Posts
    140
    LoL welcome to my world.

    Do you have different subs/functions named differently throughout the forms?
    I had this happen to me a couple weeks ago and it turned out to be because I'd 2 subs in completely unrelated forms named the same (Clr_Frm or something like that to reset the form), found those, recompiled and performed a compact/repair, and voila things started working again.

    Was truly frustrating and sounds almost exactly like what you're going through.

    Sam, just something else to check out.
    Good, fast, cheap...Pick 2.

  6. #6
    Join Date
    Sep 2008
    Location
    NM, USA
    Posts
    97

    Red face

    Quote Originally Posted by SCrandall
    LoL welcome to my world.

    Do you have different subs/functions named differently throughout the forms?
    I had this happen to me a couple weeks ago and it turned out to be because I'd 2 subs in completely unrelated forms named the same (Clr_Frm or something like that to reset the form), found those, recompiled and performed a compact/repair, and voila things started working again.

    Was truly frustrating and sounds almost exactly like what you're going through.

    Sam, just something else to check out.
    wtf, windows, wtf.

    I closed the database. Disassociated from the workgroup. Opened a different database application, joined THAT work group. Checked that the break points in THAT database's module code were recognized. Yes. Closed out of that. reopened, rejoined first database/work group.

    Everything works now. And I have absolutely not the faintest idea why.
    "Unix is user friendly... It's just very picky about its friends."

    The best things in life...are well-documented.

  7. #7
    Join Date
    May 2005
    Posts
    1,191
    Quote Originally Posted by atsukoarai86
    Everything works now. And I have absolutely not the faintest idea why.
    Why, it's because of our great advice, of course!
    Me.Geek = True

  8. #8
    Join Date
    Nov 2007
    Location
    Adelaide, South Australia
    Posts
    4,049
    Sometimes Access is like that... weird stuff goes on. I was going to suggest a DECOMPILE, Compact and Repair.
    Owner and Manager of
    CypherBYTE, Microsoft Access Development Specialists.
    Microsoft Access MCP.
    And all around nice guy!


    "Heck it's something understood by accountants ... so it can't be 'that' difficult..." -- Healdem
    "...teach a man to code and he'll be frustrated for life! " -- georgev

  9. #9
    Join Date
    Dec 2004
    Location
    Madison, WI
    Posts
    3,926
    I prefer to add in msgbox commands to return my variables or other executaions at specific coding spots. (ie. msgbox "FirstName = " & rs!FirstName, msgbox "Function XXX executing..." or msgbox "Function XXX done.", etc...)

    I (personally) find it easier troubleshooting problems this way versus using breakpoints.
    Expert Database Programming
    MSAccess since 1.0, SQL Server since 6.5, Visual Basic (5.0, 6.0)

  10. #10
    Join Date
    Nov 2007
    Location
    Adelaide, South Australia
    Posts
    4,049
    I find it easier, in the extreme, to set a stop or breakpoint and trace through misbehaving code.
    Owner and Manager of
    CypherBYTE, Microsoft Access Development Specialists.
    Microsoft Access MCP.
    And all around nice guy!


    "Heck it's something understood by accountants ... so it can't be 'that' difficult..." -- Healdem
    "...teach a man to code and he'll be frustrated for life! " -- georgev

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •