Uneditable unbound subform and I dont know why

[kelly d via AccessMonster.com]

I have a subform with no recordsource that i use to display claim info when a
claim is chosen from a listview. when that subform populates, none of the
textboxes are editable. I click in any of them, cursor blinks but I cant type,
until after I click on any of the buttons on my subform, after they run thru
their procedure, then all of my textboxes become editable. I have checked
and double checked and have even included code to ensure so, my subforms
allowedits is true, my subform objects locked property is false, all of the
textboxes locked property is false but I still cant type inside a textbox
until after I click on a button. has anybody ever encountered this and what
do you suppose is causing it.

thanks
Kelly D

 

[Allen Browne]

Did the main form start out with AllowEdits set to No?

If so the subform *control* on the main form might be uneditable, in which
case the form that gets loaded into that control will be uneditable despite
that form's own properties.

 

[kelly d via AccessMonster.com]

thanks for the reply.
I double checked again just to make sure. the main forms AllowEdits is yes,
no code changes that and just to be certain I even put a me.AllowEdits = True
in the main forms load event, the part that is baffling me is that this is
happening to 2 different subforms. there is a button on one of the subforms
that, when clicked, brings up a popup form that is a calendar, when a date is
clicked that popup closes and a date field on that subform fills with the
date that was clicked, when I click on that button to bring up that popup,
click a date to close it, then the 2 subforms are editable again. Plus, if a
main form or a sub forms AllowEdits is no, then doesnt that make buttons not
work either? Anyway, I checked the code behind the popup calendar to see if
I had something in there about AllowEdits or Locked or anything like that I
had forgotten about but there was nothing like that.

 

[kelly d via AccessMonster.com]

I think I fixed it. that <bleep> ing name auto-correct was turned on still.
1. if that feature is so unstable, why is it still in Access?
2. an amendment to the Access 10 commandments should be 'if it dont make
sense for nothing, make sure name auto-correct is turned off'
3. if I wrote a trouble-shooting book the only thing i'd put in it is 'turn
name auto-correct off. the end'

I would say that 'name auto-correct' has been the source of many long nights
scratching my head and bizarre errors, but it's my lack of memory to remember
to turn the darn thing off that is the culprit.

 

[Allen Browne]

Very glad to know you solved this, Kelly.

Agreed that this misfeature has to be a consideration in almost any problem
in Access, even with all patches applied.

It should be called "Name AutoCorrupt."

 

[kelly d via AccessMonster.com]

I whole-heartedly concur.
thanks for your help again.
kelly signing off....until my next problem.
see ya.