Forum

  • If you are new to these Forums, please take a moment to register using the fields above.

Announcement

Announcement Module
Collapse
No announcement yet.

Outlook TECH gurus? pls. HELP!

Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • Outlook TECH gurus? pls. HELP!

    When I assign an Outlook TASK to an associate within the office, they cannot open the assignment.
    Here is what it says:
    "The property does not exist. The field you want to modify is not valid for this type of item"

    When the associates assign me a TASK, I get it and can accept it.
    I understand that when I send it outside the office, but within Outlook, the other party gets it.

    Can someone PLEASE help me with this issue...???

  • #2
    Is the task you are sending him in a custom form? Also, are you using an Exchange server or just using POP? What version of Outlook are you using?

    Comment


    • #3
      Greetings Adam!

      RE:
      Custom Form? No, a standard assignment

      We have an Exchange Server but we are using both the POP 3 and the Exchange - I tried sending my associated using both, but it will not work.

      Version? 2003 Professional

      I truly hope this can be resolved, because with delegation of the assignment I can track if Things Are Getting Done...!!!

      Best regards,

      Franklin
      Last edited by fcroes; 03-24-2007, 09:23 AM. Reason: spelling

      Comment


      • #4
        I found this with some Googling the newsgroups.

        "Check your Task folder properties to see what default form is used when
        creating tasks. Right click the Tasks folder, select properties and then
        use the dropdown to see if you are using a non-default task form.

        You might also want to check to see if you are using any add-ins that create
        a custom task or other Outlook item. "

        Comment


        • #5
          Frankly - I've never seen this type of delegation work properly. I think you're much better off sending them an email and then noting in your @WaitingFor list (as well as perhaps the "Contact" field in the task if you so wish).

          Sorry not to be of more help.

          J.

          Comment

          Working...
          X