Weird Access 2K problems in a form

  • Thread starter Thread starter Chuck Chopp
  • Start date Start date
C

Chuck Chopp

I've got 2 very strange problems occurring in a form.

1) There are approximately 40 fields on the form. The first field has a
tab index of zero. If an existing record is being edited and the user hits
the TAB key to advance to the second field in the tab order [tab index 1],
then all of the fields on the form are blanked out. There are no events
defined for any of the fields, and none of the form events does anything
that should clear the fields. The form events are after update and form
load. All of the forms are bound to fields in a record and closing the form
after the fields have blanked out does not result in the actual fields in
the record being cleared. Reloading the form displays all of the fields
properly again until the TAB key is hit again.

2) The second field on this form [tab index 1] is a single character text
field with 2 allowable values - "A" [active] and "I" [inactive]. When I
first load the form for a record, I can tab to this field or click in it.
However, once I change the value of the field, suddenly the field becomes
locked and I can't edit it again even if I save the record, close the form
and re-open the form. Again, there's no macros or VB code set up to handle
events for any of these fields.


Any ideas what might be going wrong? This only happens on this one form in
an application that has 25 or so forms.


TIA,

Chuck
--
Chuck Chopp

ChuckChopp (at) rtfmcsi (dot) com http://www.rtfmcsi.com

RTFM Consulting Services Inc. 864 801 2795 voice & voicemail
103 Autumn Hill Road 864 801 2774 fax
Greer, SC 29651

Do not send me unsolicited commercial email.
 
Update for problem #2:

On the form exhibiting this problem, the status code field was set to right
justify the value. All other status code fields on the other forms were set
to general alignment. After changing the status code field to have general
alignment on this form, I can tab through the fields and get the cursor to
enter the status code field on the form. However, there's something strange
still happening. If the status code is "A", then tabbing into the field
results in the value being selected [e.g. highlighted] so that you can type
a single character to replace it. The valid values are "A" and "I". If the
status code is "I", tabbing into the field results in the cursor
disappearing. The status code field still has focus, but you need to hit
the left or right cursor keys to make the cursor reappear.

Is this some sort of a bug with MS Access 2000?


TIA,

Chuck
--
Chuck Chopp

ChuckChopp (at) rtfmcsi (dot) com http://www.rtfmcsi.com

RTFM Consulting Services Inc. 864 801 2795 voice & voicemail
103 Autumn Hill Road 864 801 2774 fax
Greer, SC 29651

Do not send me unsolicited commercial email.
 
I would start by replacing the Status Code text box with a
new one. I have had text boxes become unruly without my
ever knowing why. You could compact and repair the
database, and export the objects to a new blank database.
Are the Allow Edits, Data Entry etc. properties of the
form the same as on the forms that work properly? When
you tabbed and found blank fields, were you still in the
same record, or had you moved to a new one? These are
just a few scattered thoughts that I am posting because I
see you have received no other replies.
 
Bruce said:
I would start by replacing the Status Code text box with a
new one. I have had text boxes become unruly without my
ever knowing why. You could compact and repair the
database, and export the objects to a new blank database.
Are the Allow Edits, Data Entry etc. properties of the
form the same as on the forms that work properly? When
you tabbed and found blank fields, were you still in the
same record, or had you moved to a new one? These are
just a few scattered thoughts that I am posting because I
see you have received no other replies.

I will be doing a compact & repair on the database later today. I have one
MDB file for code, forms, reports, macros, etc..., with links to tables in a
separate database that has nothing but tables in it.

I will also try deleting the text box control for that field and re-create
it from scratch.

The cycle property is set to "current record" so I don't see how the form
could have navigated to another record. The other properties are set to
allow editing of the current record but no new records can be added via this
form.


--
Chuck Chopp

ChuckChopp (at) rtfmcsi (dot) com http://www.rtfmcsi.com

RTFM Consulting Services Inc. 864 801 2795 voice & voicemail
103 Autumn Hill Road 864 801 2774 fax
Greer, SC 29651

Do not send me unsolicited commercial email.
 
I was just guessing about a things that sounded similar to
what I have seen in my own projects. Good luck.
 
Back
Top