Avatar

Level 3

Hi

Probably you are right and IE thongs who hold "in use" in question form (which propisie failure to save), but unfortunately this does not solve my problem.

It does not really worry me too much not to save the file itself, what worries me is that the event is invoked when postSave NOT BEEN SAVED.

If the postSave event is not invoked would have no problem, since the user would see the error message and might try to save it again, under another name, but the problem is that invoking the event as if everything had gone well.

What should be the behavior of the mechanism to saveAs and associated events if an unexpected error occurs as in this case?

I see no coherent or logical the current behavior of mechanism

I can not tell customers "Gentlemen this is the fault of IE" ... nor can I say "when they download the PDF, do not open the file directly, keep it in a diferent folder and then open it ...". Expected (at least for me) was that the event postSave be invoked only when the PDF is saved correctly, regardless of the causes of failure that prevents saving.

It is very hard to work with the Adobe PDF / Designer / LC platform... to do simple tasks, develop small applications/pdf forms over controlled environments, everything is fine, but when you need to integrate the platform into complex processes, with a variety of clients / environments (XP, Vista, W7, Reader and Acrobat 8,9, IE 7,8) arise multitude of "small" problems in which one developer many times (as in this case) can not provide a solution, it is really frustrating.

The only thing I can do right now is not to use the event postSave and consider a new mechanism to manage my PDF forms, not sure yet how I will do this.

Thanks anyway, and excuse my basic level of English.