Thanks for the quick reply Clay.
Yes unfortunately due to the requirements of drilling right down to the nitty gritty details within the form - I had to write some code to cycle through it to populate a seperate SharePoint list for use with our financial system using SharePoint's update list webservice.
The server has the right mail settings on - I know this because when I create the Approval Workflow and associate it with my forms library, I get emails from SharePoint when an approval is needed to take place, but the link it provides takes me to a page which simply states "The form is now closed" - a very useful error message from Microsoft as usual...
I've read this is to do with the feature being corrupt some how but I've just removed all knowledge of the project from our MOSS server and redeployed and the error remains and all the articles I read seem to assume you are creating a custom workflow using VisualStudio, which I am not (though I will probably need to at some point)
I'm so frustrated because this is pretty much the last task and the workflow seems to be assigning it all correctly, just not providing the correct link to open the form in the browser (when I view the workflow's assigned approval task manually, I can download and open the form.xml and approve or deny it locally perfectly, just not via the server which was the whole point of purchasing MOSS enterprise!)
Has nobody else had this same Form has been closed problem whilst simply deploying a Form and attaching the SharePoint approval workflow?
John