Printable Version of Topic

Click here to view this topic in its original format

UtterAccess Forums _ Access Forms _ Subform Record Selectors

Posted by: BobDarlington Dec 7 2017, 01:34 AM

I have a continuous subform with record selectors to the left of each record.
When a user clicks on the grey selector button and presses arrow down, the selector moves down but skips one record each time.
If they click into a field in the record, then the down arrow works as expected.
Similarly, if the vertical scroll bar is slid to the bottom of the list, it won't display the final record in that list. You need to select the down arrow at the bottom of the scroll bar to display that record.
Any help appreciated as always.
Bob D

Posted by: Art_Of_War Dec 7 2017, 04:00 AM

During my last semester of database design studies in my IT course, we were advised NOT to use record selectors or the navigation bar on forms, or for that matter, subforms.

Instead, we added buttons, i.e. "Add Record," "Open Form," "Save and Close," etc. etc. I can show you an example if you like:



It's a lot cleaner and more user-friendly if you get rid of the extra properties and customise the form. It just looks more professional.

Posted by: GroverParkGeorge Dec 7 2017, 07:33 AM

What you describe seems to be out of the ordinary for form behavior, but there's more going on than one can surmise from this description, unfortunately. In trouble-shooting, we might start with the most obvious things first, and then move on to the less obvious if needed.

What do you have set for the cycle property of this subform?


Are there any controls on this subform which have some sort of tabbing behavior set for them? How about the controls themselves? When you enter a new record, which control gets focus first? Which one gets focus last?

I am assuming that your subform is editable, but that's also something to account for.

Posted by: BruceM Dec 7 2017, 08:16 AM

QUOTE
During my last semester of database design studies in my IT course, we were advised NOT to use record selectors or the navigation bar on forms, or for that matter, subforms.

Out of curiosity, how did they suggest you navigate the records?

Posted by: River59 Dec 7 2017, 08:39 AM

You can add buttons for first, next, previous and last, Bruce.

Posted by: GroverParkGeorge Dec 7 2017, 08:46 AM

I have, from time to time, replaced the built-in navigation buttons with custom buttons. Sometimes a busy form with multiple subforms can be a bit confusing when it's not clear which set of navigation buttons control what.

That said, the question here is not about navigation buttons, but about record selectors, if I'm reading the OP correctly.

Posted by: GroverParkGeorge Dec 7 2017, 08:47 AM

hm. I note that you have a subform in this screenshot, and that the subform would appear to have a record selector. Isn't that going to be the case for forms in datasheet view?

Posted by: BruceM Dec 7 2017, 09:36 AM

QUOTE
I note that you have a subform in this screenshot

George, I think that was posted in a response. I don't see that Bob D (the OP) posted a screen shot.

QUOTE
You can add buttons for first, next, previous and last

Yes, I know that. I do it often. I was just curious as to what they suggested in the class.

But I agree with George, the question was about record selectors. I should not have taken the detour.

I have experimented with various settings on the Property Sheet, but cannot replicate the problem. To Bob D, you could try creating a new form, and copying the controls from the old form to the new one. Other than that all I can suggest is to post a stripped down copy of the database, with any personal or sensitive information removed. Maybe somebody here can spot something.

Posted by: missinglinq Dec 7 2017, 09:39 AM

QUOTE (GroverParkGeorge)
...What you describe seems to be out of the ordinary for form behavior...


I think that this really pins down the issue, here! The behavior described isn't normal, whether you're talking about a Continuous View or Datasheet View Form, with the Cycle Property set to All Records or Current Record.

What this describes, in essence, is what I call Strange, Odd and Curious Behavior, which usually translates into corruption of the Database, in one form or another. Barring some custom modification of navigation behavior, by the developer (and I would assume that the developer would know if such modification was in place) I think you pretty much have to go with this assumption.

The standard approach, for this type of thing, is to create a new, blank file and import everything into it. Only takes a minute or two to create and check out, and if it doesn't work you haven't really lost anything! And, amazingly, it does frequently work!

Linq ;0)>

Sorry...got distracted by dog needing to go out and missed Bruce's last post, which is pretty much duplicated by mine! ohyeah.gif

Posted by: GroverParkGeorge Dec 7 2017, 09:51 AM

Correct it was in a response, not the OP's post and it was intended to point out that even when one DOES eliminate navigation from some displays, it's not possible to do it everywhere.

Posted by: BruceM Dec 7 2017, 10:14 AM

QUOTE
Bruce's last post, which is pretty much duplicated by mine!

Not really. I only suggested remaking the form. Importing everything into a new, blank database may be a better place to start, and is actually simpler in most cases than re-creating a form. If the problem still persists after that, re-creating the form could be the next choice.

Posted by: BobDarlington Dec 7 2017, 05:48 PM

Thanks to all for your responses.
It turns out that I had a KeyDown routine which caused the problem to occur.
Now all I have to do is work out why I added that routine in the first place :-)
My own documentation leaves something to be desired.
Thanks again
Bob D

Posted by: GroverParkGeorge Dec 7 2017, 06:23 PM

Congratulations on solving the mystery.

Continued success with the project.

Posted by: BobDarlington Dec 7 2017, 08:59 PM

Thanks George.
The KeyDown event caused the Record Selector problem, but the vertical scroll bar issue was resolved by resizing the height of controls in the continuous subform.