I've been very busy and as such haven't had time to test any suggestions or
to respond, thus the lateness of this reply.
On the forms design view, using the Control Toolbox, I add a checkbox, right
clicking on it I select PROPERTIES and on the VALUE tab, I select NEW. This
binds the control to a new field...using the PROPERTIES window.
When I select NEW (field), another window pops up allowing my to select the
TYPE of data associated with the field. After that is selected, the FORMAT
field's selection changes based on the TYPE.
Since the proposed problem with my form is that of an improper TYPE
associated with a particular control, my further question is Is there a
source that tells me what the valid TYPES that can be assigned to each
Control?
Also, if the fields are improperly bound (control to type), then why can I
open, manipulate and save the form locally?


"Hollis Paul" wrote:

In article ,
=?Utf-8?B?Qm9iVA==?= wrote:
The custom controls are just the
standard ones that are available in design mode. I do add them as 'New
Fields' in the Properties window. The form has several pages and is fairly
busy with check boxes and labels.

I have not done anything with task form in ages, so I am no expert on these
things. However, the quoted statement does not make any sense. A control is
not a property. You have to create custom fields to which you bind the
controls. Custom fields have types. You have to use the right type of
custom field to hold the data that the custom control produces. If you are
really as clue-less as the above sounds, then that is your problem--one of
the controls requires a field other than a text type field.

Not to worry if you can't find an obvious mismatch. The rule is to throw
away the first design, maybe the first three, because you won't get it right
the first time out of the box.

So, on this next design, create a new form in small steps--that is, just a
small number of controls per step. Publish each step with a name of the
canonical form MyFormName_verNNN, and increment the NNN field with each
publication. Run the new version and when you get that error again, you will
know, within a the few controls on the step, which control is causing the
problem. That step will be a lot easier fix than your multi-tab with lots of
controls. Publish to only one place, like the Exchange Organization Forms
Library, but move older form designs to the personal forms library of a PST
file for safe keeping. Keep at least three generations of the developing
form, so you are never kicked back to square one.

--
Hollis Paul
Mukilteo, WA USA