Anyone else with record offset problems using ContinuousFormsCurrentRow logic?

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • LHodgdon
    New Member
    • Aug 2008
    • 1

    Anyone else with record offset problems using ContinuousFormsCurrentRow logic?

    Hi,

    Has anyone else had a record offset problem using the ContinuousForms CurrentRow sample database (2007 Access.) The rows seem to be off by one. Would really appreciate the help!

    Thanks in advance.

    Laurie
  • malcolmk
    New Member
    • Sep 2010
    • 79

    #2
    Not sure what you mean but at a guess, are you expecting record 0 to report that it is actually record 1 ? unless you change the base setting (I think thats what it is) counting indexes begin at 0 upward and not 1.

    Comment

    • RuralGuy
      Recognized Expert Contributor
      • Oct 2006
      • 375

      #3
      Where would we find that sample db?

      Comment

      • Whizbang1982
        New Member
        • Jan 2013
        • 5

        #4
        Find this (in the Private Sub ctlTextBox_Mous eMove):
        Code:
        ' Calculate which row we are on adding in the ScrollBar Thumb offset.
        lngTemp = (sngY \ m_Form.Section(acDetail).Height) + lngRet -1
        and replace with this:
        Code:
        ' Calculate which row we are on adding in the ScrollBar Thumb offset.
        lngTemp = (sngY \ m_Form.Section(acDetail).Height) + lngRet
        At least, that seems to have fixed it. Though be aware that this class doesn't seem to work in 2007/2010. It doesn't sense the scroll bar position.

        Sample DB here: http://www.lebans.com/conformscurcontrol.htm

        Comment

        • Whizbang1982
          New Member
          • Jan 2013
          • 5

          #5
          In Private Function fIsScrollBar

          Change "scrollBar" to "NUIScrollb ar" (or maybe LIKE "*scroll*" instead of =) and undo the last edit I suggested.

          Comment

          Working...