CHKMSTrainer said:
Inside an existing database converted from 2003 to 2007, old functionality
in
the bottom navigation bar of the form view there was the ability to type
in
information to search, it would default to a particular field-now it
defaults
to any information matching what you've typed in. Can this be changed?
I don't think so. I suppose you could make your own, but then again why not
just use ctrl-f? (less work then using mouse to click on a box).
ctrl-f works in word, excel, and just about everything else. I used access
for 10+ years and NEVER even knew that you could type in a search into the
record navigation box (thought you had to type in a number). You can well
see that in 2007, they split (moved) the box to separate search box because
I
never seen ANYONE ever use that feature prior to 2007. So, I think it is
great they moved the search out, but I don't know how to change the default.
I think the best work around here is ctrl-f. ctrl-f gives you the option to
search any part of field, whole match, and also gives you the option to
select what field (whole table, or current column).
When going through records via the next
button old functionality had it where you could hold the button down and
move
through several records at once-new functionality is one click per record.
Has this function been changed as well?
I suspect it has, but then again it really hard to "guess" how many records
you going to move, and even worse in a network situation, you going to cause
some real serious performance problems. Teach the users to use page down. I
for one would NEVER allow a repeating button action and you really don't
want users to start "learning" the idea of holding things down to function.
The whole web never works this way, most users will never get the
"timing/skill" down pat to utilize this approach correctly, and it just
really a bad practice for moving through data.
You *can* put your own button in the forms footer and specific set the
button to allow "auto repeat". You can find this option in the "other" tab
of the property sheet. I really strongly recommend against using buttons
that fire while you hold down the mouse, they are simply too hard for users
to control, can cause bandwidth problems when using a network, users can't
get the timing down to move one record, or 5 records. New users don't have
years of mouse skills, and they tend to hold down and click on the mouse
quite heavy (and, if the button starts to repeat, the user gets very
frustrated).
Even worse is often the code in the button is not yet finished before it
tries to fire the code again (this is especially so when using any type of
activeX control on a form, it will cause access to crash).
If you must however, the code behind the button could be:
On Error Resume Next
DoCmd.GoToRecord acActiveDataObject, , acNext
I will ask a few other people and develoeprs what they think on this
issue...but you are the first person to bring this up in the
newsgroups.....interesting and I learn new things here every day...
