Keyboard Option (Select Entire Field)

[Guest]

For data entry purposes I would like for the full field to be highlighted
when I tab from one to the next, so that the new entry totally replaces the
previous values.
Under the Tools/Options/Keyboard menu there is a choice for "Behavior
entering field" which sets this preference, but when exiting and reentering
Access the behaviour defaults back to "Goto the End of the Field".

Is there a specific place where such options are saved?
The help of this community is appreciated.

 

[Guest]

Hi Gino,

You are changing the setting in the correct place. There must be some reason
that the setting is not staying set. Perhaps your database is starting to
corrupt (?), or there is startup code that is setting it back to Goto the End
of the Field. If this is an unsplit, but shared database, then some other
user may be changing your selection. Usually, the setting you made should
stick.

Tom

http://www.access.qbuilt.com/html/expert_contributors.html
__________________________________________

:

For data entry purposes I would like for the full field to be highlighted
when I tab from one to the next, so that the new entry totally replaces the
previous values.
Under the Tools/Options/Keyboard menu there is a choice for "Behavior
entering field" which sets this preference, but when exiting and reentering
Access the behaviour defaults back to "Goto the End of the Field".

Is there a specific place where such options are saved?
The help of this community is appreciated.

 

[Guest]

Thank you Tom for the very quick response.
The inability for the keyboard option to stick is annoying but since you
mentioned corruption, I am now worried about deploying the beta system to a
client in a couple of days.
Indeed, I have had problems with the database crashing unexpectedly and I
had to rebuild it several times importing all forms, queries etc into a new
blank database.

(At times I even rebuilt forms by saving the module in a text file, then
copying just the objects into a new form and pasting back the code from the
text file, as suggested somewhere in the knowledge base).

The database is split but I am the only user testing and noone else is
changing anything. I will try setting the preferences in the linked tables
database to see if that
by any chance overwrites the preferences of the front end database.
However, if you have any suggestions regarding how to identify and eliminate
the corruption source in the data base, this would also be very very much
appreciated.
Thank you very much.
Gino

 

[Allen Browne]

Tom is right that the value should stick.

You can read the value with:
Application.GetOption("Behavior entering field")
and set it with the SetOption method.

 

[Guest]

Hi Gino,

However, if you have any suggestions regarding how to identify and
eliminate the corruption source in the data base, this would also be
very very much appreciated.

Check out the information that Allen Browne and Tony Toews have made
available on the subject of JET database corruption:

Preventing Corruption
http://allenbrowne.com/ser-25.html

Corrupt Microsoft Access MDBs FAQ
http://www.granite.ab.ca/access/corruptmdbs.htm

Tom

http://www.access.qbuilt.com/html/expert_contributors.html
__________________________________________

:

Thank you Tom for the very quick response.
The inability for the keyboard option to stick is annoying but since you
mentioned corruption, I am now worried about deploying the beta system to a
client in a couple of days.
Indeed, I have had problems with the database crashing unexpectedly and I
had to rebuild it several times importing all forms, queries etc into a new
blank database.

(At times I even rebuilt forms by saving the module in a text file, then
copying just the objects into a new form and pasting back the code from the
text file, as suggested somewhere in the knowledge base).

The database is split but I am the only user testing and noone else is
changing anything. I will try setting the preferences in the linked tables
database to see if that
by any chance overwrites the preferences of the front end database.
However, if you have any suggestions regarding how to identify and eliminate
the corruption source in the data base, this would also be very very much
appreciated.
Thank you very much.
Gino

 

[Guest]

Thank you Allen,
I will try reading and setting the option from within the code and see if I
can make the behaviour stick.
Gino

 

[Guest]

Wow Tom, I didn't know that there are so many ways to screw up things in
Access and I will now try to review the code for instances of code omissions
and follow other suggestions in the articles.
For instance, I thought that setting an object to "nothing" would
automatically take care of "closing".
Thank you again.
Gino

 

[Guest]

Hi Gino,

You're welcome.
If you send me a private e-mail message, with a valid reply to address, I
will send you a list that I have compiled over the years that should be
helpful as well. Here is a KB article that you'll want to look at, and likely
bookmark for future reference:

How to keep a Jet 4.0 database in top working condition
http://support.microsoft.com/?id=303528

In particular, make sure that the operating system, the installation of
Office, and the JET database engine all have the latest service packs
installed. This KB article includes instructions for how to do this.

Thank You for marking my replies as answers. This is appreciated.

Tom

http://www.access.qbuilt.com/html/expert_contributors.html
__________________________________________

:

Wow Tom, I didn't know that there are so many ways to screw up things in
Access and I will now try to review the code for instances of code omissions
and follow other suggestions in the articles.
For instance, I thought that setting an object to "nothing" would
automatically take care of "closing".
Thank you again.
Gino