Lock field in form or remove from tab-order?

eepok

Noob. Well, mostly noob.
Local time
Today, 15:24
Joined
Oct 30, 2007
Messages
112
Hello again, all. Thanks for the help with the cascading combo box, but I have another newb question(s) and request for advice. My situation is as such:

In one form (MainOrder) I have fields on the left for data to be entered and fields on the right to display information (PubContactInfo) relative to a selection from a list (Publisher). I do not want the data on the right to be editable in this form because the users are used to tabbing through everything and they are likely to accidentally edit the Contact Info. (I have a button that opens up another form with which users can edit entries.)

1) Is there a way to take fields OUT of the tab-order so that they're skipped?

and/or

2) Is there a way to lock the fields so that they cannot be edited in that form only?
 
I would think the simplest thing to do would be to disable the controls...


???
ken
 
I would think the simplest thing to do would be to disable the controls...

My apologies, I should preface my questions with this qualifier:

I'm familiar with database design and have made many a fabu DB with FMP, but an still unfamiliar with the Access versions of DB vocabulary. Thus, "disable the controls", however correct, is too vague for me to implement.
 
bah, I found it. Using (" ") in a search for the win!

Tabstop setting in the field settings -- set to "no" and you will not cycle through that field.
 
fyi - Turning tabstop off will still leave the fields editable...


:)
ken
 
Even if Tabstop is set to no a user will still be able to maunally enter the control. I suggest you follow the advice of Ken Higg and disable the controls. Go to Control Properties > Data > Enabled and set to No.
 
You could just set the Control to LOCKED.
Control Properties > Data > Locked = YES

Its right under the Enabled one.

Thats how I keep people from changing data.
 
Even better!

Thanks for holding my hand through this. I will acquire the vocabulary eventually.
 

Users who are viewing this thread

Back
Top Bottom