Quote:
Originally Posted by Father
Crap... so I should have stuck with Form Fields rather than convert everything to Content Controls.
One of the reasons I thought using the content controls would be better is that for drop downs it still allows you to enter other words into the field. Can normal form fields do this as well?
|
That is not possible with dropdown content controls; only with combobox content controls. There are ways of simulating this with a dropdown formfield (there is no combobox formfield) - but that, too, requires a macro.
Quote:
Originally Posted by Father
I also did it because some of the information I was putting in normal form fields was getting cut short. That might have been more a result of the table cell size they were on and I was blaming the fields.
|
Probably.
Quote:
Originally Posted by Father
So you mentioned that form fields don't work well with content controls. Is that in general terms on or only when you're trying to relate/connect one type with the other?
|
It's in general terms, but especially when checkboxes are involved or you're trying to tab from formfields to content controls then back to formfields again.
Quote:
Originally Posted by Father
For my sample, if I use form fields for the calculating fields but left the control control fields for the static information in other parts of form, will it cause problems?
|
Possibly.
Quote:
Originally Posted by Father
Macros scare the heck out of me... because I'm just not that familiar with coding. But I was able to remove the comments so that each new table has a specific numbered bookmark. VERY NICE!!!
|
I don't understand what you mean about removing comments - there is no need to remove comments from the macro code. They are never executed; they just explain things. They also have no connection with table bookmarks.