I have created a custom Task form based on the standard Task form. It
contains no code, just custom controls. 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.
The problem is that when I use the "Assign Task" button to send it to
another user, that user cannot open the task/form/inbox message. The error
message generated is "Can't open this item. Could not complete the operation.
One or more parameter values are not valid."
I have scoured the internet and the various forums for some insight, but
nothing solves the issue.
I have learned a variety of tips and steps to take in similar situations,
but nothing has worked.
I have, using Exchange System Manager, assigned full permissions of the
Organization Forms Library to all of my test users.
I have successfully published and my test users have opened and acted upon
these publish custom forms (all based on task)...
A simple task form (added text in the notes section)
A task form with an additional page with a 'Task field' added
A task form with a custom control added.

So, any ideas to try?

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

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

In article ,
=?Utf-8?B?Qm9iVA==?= wrote:
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, t

It appears that you are indeed selecting the type for the field. The question
really is: What are you selecting at this point? You should be selecting
Yes/No 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?

You can go to the All fields tab, in design mode, select one of your UDF's,
and down on the bottom will appear a control that lets you select from the
available types. You should be able to see the list of valid types there.

Also, if the fields are improperly bound (control to type), then why can I
open, manipulate and save the form locally?

This means that you have published the form somewhere and I am betting that
you published it to your personal forms library. If that is true, then only
you will be able to use the form on this one computer. Are you using an
Exchange server? If yes, then you should publish the form to the
Organizational Forms Library on the Exchange server. Otherwise, you need to
save the form as an OFT file, and send that OFT file to all the recipients,
telling them to open it and publish it to their personal forms library using
the same name as you use. Finally, make sure that, in design mode, you have
unchecked the box that says to send the form definition with the data item.

--
Hollis Paul
Mukilteo, WA USA