I was waiting for the Why question. The application is a bit weird and unconventional. I have a form that looks like a data entry form, but data entry is turned off. There is not a lot of data. In textbox controls on the form, in lost focus events, I can open combo boxes that allow users to select items that may be needed to added to the record. When I go to the next record, I want to have the popup boxes vanish and revert to null. I have the code to do that, but it would be handy to have when I change from one record to the next. Based on your answer, how would I give the current record the focus in such a layout. I could close the popups as I leave them, but it would helpful if they could be seen till I go to the next record. Hope this make s modicum of sense.
I just added record navigation buttons to the form and can control thing in those, I think. Not elegant, but workable.
Data entry is disabled, but you still want to update the records.
Do I need to set the behavior of the enter key for current event fires?
Something about Great Minds, is involved here. Like the thumbs up, gave me the warm and fuzzies (Old IBM term)Data entry is disabled, but you still want to update the records.
Scrolling itself isn't going to work, but there are other ways to move focus from one record to the next.... and while I was typing you discovered the record navigations buttons.
It is not the navigation buttons that give you control, it is the form level event procedures that give you control over how a form behaves.
No, do NOT change the behavior of the enter key. Control the scrolling by setting the Cycle property as I described above to force the user to use the navigation control. You do NOT need to create your own navigation control. It isn't any better or more user friendly than the built in option but it may look nicer so use your own controls if you want. Just make sure you download a version that lets you reuse the controls on all forms without having to write code for each instance.
Whatever happens, if I create navigation buttons, is the same for each button. I was going to create a subroutine or a module that does the cleanup, that way I won't have to code for each. But the Current event seems better. Mostly because you say it is, and after rereading it, it makes more sense. Only one place to put the code for everything I need. And, no need to clutter up the screen with more controls.
Thanks. That analogy doesn't help people who have no programming experience but that epiphany really helped me when it came to me after a year or two of struggling to figure out how to actually use the event model to my advantage instead of feeling like I was fighting an uphill battle
I'm glad you found it helpful. Just remember there is almost certainly ONE SINGLE event that will solve your problem. You just have to figure out what that event is Sometimes, it will seem like the choice of events is equal but when you dig deeply, it is almost never equal. One will surely be better than another. For example, I had one person argue with me about why he thought the lost focus event was the "correct" event for validation because he liked the idea that Access wouldn't let you leave the control. That's why I made it the star of the second video where I show how that event fails to stop Access from saving invalid data no matter how promising it looks on the surface.If I could, I would give you an apple.Thanks. That analogy doesn't help people who have no programming experience but that epiphany really helped me when it came to me after a year or two of struggling to figure out how to actually use the event model to my advantage instead of feeling like I was fighting an uphill battle
I don't know if you ever saw this thread but if you haven't seen it, do take a look. Building this sample to show WHY the BeforeUpdate event is the best event for data validation actually was an eye opener for me. There are two videos which have gotten good reviews based on my PM's. The database I used is a recent addition to the thread. you can use the forms I used in the videos or you can make your own to test specific circumstances.
Bad Data is Bad for Business #1 and #2
I just added #2 --- that link is further down. It is much shorter than #1. I also added a copy of the database I used for the video. Enjoy:) I created a database to help people to understand how and why to use the Form's BeforeUpdate event to validate data. @Uncle Gizmo and I made a...www.access-programmers.co.uk
I've AND'd bits because Microsoft assigns meaning to individual bits in certain operations but never had to remove them or swap them. In the relational universe, this would be the equivalent of mushing attributes together into a single field which would make it non atomic and therefore violate first normal form.
That's clever. Xor would work correctly in VB
I do virtually no bit manipulation so although I know that XOR exists, I don't believe I've ever used it in any program I've written in 50 + years
I do believe I mentioned that.
Minor epiphany. The events in ACCESS are like user exits that came in older software. Early versions of IBM's supervisors had user exits, as I remember from the ferrite core days, or I might be confusing it with other software. i ts a a place in an application where you could put a bit of your own , custom code, to augment the application to your fancy.
