My apologies to Craig, who posted a comment to my earlier post about our FBA problems and I didn’t notice until today.
To update you all on the situation, the fault is still with Microsoft and I have not yet received a hotfix.
However, for anybody considering FBA in their deployment, I would not let this issue stop you. There are two reasons I say that:
Hopefully this answer’s Craig’s question and assuages any doubts about the wisdom of deploying FBA in your SharePoint solution.
I posted last week about a couple of issues we were experiencing with SharePoint. I made some traction on the Workflow History issue at the end of last week and the revelation was pretty far-reaching, so I’m posting again.
It turns out that the stuff I said about systemupdate was wrong… up to a point.
There is a bug with systemupdate and triggering events, but it’s not the one we thought it was! It turns out that the behaviour we are seeing is correct - systemupdate is supposed to trigger events, just not update things like the modified by and last updated columns. It’s actually the behaviour within a workflow which is at fault, in that events aren’t being triggered when they should be.
