Hi Bruce,
unfortunately, the GebtBytes() "trick" did not solve the problem.
However, we could find out in more detail what the problem is: The
workflow fails to change the InfoPath document after it has been
changed in InfoPath by another person.
The workflow is like this:
First, the InfoPath document is written by a user and published in
SharePoint.
Second, this document is taken by the workflow and new forms are
created and stored in SharePoint.
Third, a person (the user's chief) approves these new forms. His
decision is stored in the form.
Fourth, the workflow takes these forms.
Now, the workflow can read the form, but it can't make any changes to
it.
We granted the document's access rights so that the user, that runs IIS
(and, thus, the Workflow Foundation, we assume), always gets full
access to each document.
However, the problem is still there, and documents which have been
changed by some other user in InfoPath can't be overwritten by the
Workflow Foundation.
Does anyone have a clue about this?
Or knows how the rights have to be granted exactly?
Thanks!
Christoph
On Jan 25, 4:59 pm, "christoph.han...@googlemail.com"
<christoph.han...@googlemail.com> wrote:
> Hi Bruce,
>
[quoted text clipped - 21 lines]
> > cheers
> > Bruce