Thanks for your input, you two. I figured it out myself, however.
The problem is that, as you know, for some reason a form with the dialog
border style sizes not according to the physical dimensions of the form, but
to the size of the form design window when normalized (is that a bug or
what?). I had it sized too small that way, so when viewed in form view, the
form was too small to for the subject control and the subform. The fix was
to enlarge the normalized form design window sufficiently for all of the
controls/elements to show.
That still does not answer why enabling tab stop for this control
"increases" its size such that it is no longer visible on the form in form
view, nor why, instead of clipping the subform at the bottom or the text box
control at the top, the textbox control is bumped entirely off the form.
FYI, I'm using WinXP, on a 2.4 GHz laptop with 512 MB RAM, so system
resources don't appear to be a problem.
"NeilAnderson" <ne***********@boroughmuir.edin.sch.uk> wrote in message
news:83**************************@posting.google.c om...
Steve Jorgensen <no****@nospam.nospam> wrote in message
news:<2c********************************@4ax.com>. ..
Try setting the enabled setting to false.
Neil
I've never seen that precise symptom, but I've seen all kinds of odd
behavior along those lines when resources are low. Which version of Windows are
you using?
On Wed, 09 Jun 2004 04:11:32 GMT, "Bryan Capps" <br********@cfl.rr.com>
wrote:I have a text box control on a form, the value of which is calculated
(concatenated) from entries on a subform. Accordingly, I've set the
control's locked property to true and the tab stop property to false.
Thelatter setting makes the control completely disappear.
FYI, the form is dialog border style. When set to sizable border
style, thecontrol only appears when the form is re-sized much larger.
I have a similar form with a similar txt box control with identical
settings, and it doesn't disappear.
I've recreated the form to determine why the textbox control
disappears, andsetting the tab stop property to false appears to cause it.
Anyone else have this problem?
Bryan Capps
br********@cfl.rr.com
