Junkee Brewster
Registered User.
- Local time
- Tomorrow, 02:23
- Joined
- May 21, 2005
- Messages
- 33
The Return of the dreaded mousewheel! I have used the fab Search option on this topic, but I feel I have some requirements that prohibit me using some of the options available. I need to allow its use for navigation of the mainform, but totally block it on the subforms, but with lots of conditions!
The database in question is NOT mine, and it's already built. If it were one of mine, I'd simply block the darn thing entirely or adopt some of the example databases I found (ghudsons was the kind of data verification I can dig, and a few in A97 format were good too).
I have to cater for workmates that are strangly fussy, rather lazy and totally unappreciative of order. Who would have though enforcing uniform entry of dates from 20 different ways (I counted) to one way, was such a contentious issue? OR, a BAD idea? Sigh.
As a result, I cannot be seen to have done ANYTHING to its function. So, I cannot have:
*Any form of "save" each record or blocks or anything like that
*Any form of validation boxes or message boxes popping up
*No dlls (if possible)
*In a nutshell, no extra effort - Type 'n' go - it has to be a secret
*And, I can't block the mousewheel from scrolling through personnel in the mainform.
I have to eliminate the RAMPANT creation of duplicate subentries (like, you're still on the one record in the main form, but if you're not paying attention and wheel in the subform, you flick over to the new row and type, and POW).
Am I dreaming? Is there some easy solution in form setup that I'm overlooking? (the problems of self-education, you are often unaware of some of the simplest little options). I aplogize if this solution has been presented before on the board, but it is likely I didn't not understand what I saw properly, or I felt it wasn't quite what I wanted. Thanks very much.
The database in question is NOT mine, and it's already built. If it were one of mine, I'd simply block the darn thing entirely or adopt some of the example databases I found (ghudsons was the kind of data verification I can dig, and a few in A97 format were good too).
I have to cater for workmates that are strangly fussy, rather lazy and totally unappreciative of order. Who would have though enforcing uniform entry of dates from 20 different ways (I counted) to one way, was such a contentious issue? OR, a BAD idea? Sigh.
As a result, I cannot be seen to have done ANYTHING to its function. So, I cannot have:
*Any form of "save" each record or blocks or anything like that
*Any form of validation boxes or message boxes popping up
*No dlls (if possible)
*In a nutshell, no extra effort - Type 'n' go - it has to be a secret
*And, I can't block the mousewheel from scrolling through personnel in the mainform.
I have to eliminate the RAMPANT creation of duplicate subentries (like, you're still on the one record in the main form, but if you're not paying attention and wheel in the subform, you flick over to the new row and type, and POW).
Am I dreaming? Is there some easy solution in form setup that I'm overlooking? (the problems of self-education, you are often unaware of some of the simplest little options). I aplogize if this solution has been presented before on the board, but it is likely I didn't not understand what I saw properly, or I felt it wasn't quite what I wanted. Thanks very much.
