HiYou may find this blog posting gives you some background.http://www.avoka.com/blog/?p=166The real problem you're facing is that LiveCycle is a very complex product, and you're seeing log messages from lots of different modules and sub-systems all rolled up into a single file. Hang in there, it wil...

Sounds like a bug to me. Or at least some "behaviour" that isn't optimal. I'd log this with Adobe support.Howard

You'll need a fax server - effectively a fax machine that saves the incoming fax to a directory rather than onto paper.Alternately, there are several fax server providers who will do this online for you.Like Jasmin says, once you've produced the file, you can use it to kick off a LIveCycle process, ...

Um, I don't quite get it. (And no, I haven't tested this...)Are you saying that if you:Delete the fragmentUpload a new version of the fragement Open the XDP form that refers to the fragment--> You get the old version of the fragment?   4.   But if you close workbench, then open it again, and then op...

Hi Elaine1. Yes, I agree, this isn't something you should need to code up yourself, it should be part of the product. My understanding is that this area is targetted for improvement in the next version, but you may want to log a feature request with Adobe to make sure it works the way you'd like it ...

Hi SteveMy understanding is that deleteResource deletes the entire resource, with all its versions.What Elaine wants to do is to delete old versions of a resource, but retain the most recent version. (Elaine, please confirm.)You can get old versions of the resource using getHistory, but there is no ...

Hi ElaineI had a quick look at the APIs.There is no exposed API for removing old versions.Therefore there is no way (at the moment) that anyone could write a utility for purging old versions.I suspect your proposed approach (i.e. delete the entire resource before uploading a new version) would be th...

HiIt sounds to me like one of the instances of Forms executable is dying due to invalid font, and is then failing for subsequent renders. The reason that it's intermittent may be that you have multiple instances of the Forms executable, and one of them has failed, and the other(s) are okay.One thing...

Thanks MarkSo a component to simply test the validity (well-formedness) of an arbitrary XML document would be helpful?This would save you having to write the file to the file system, and read it back again.By the way, do be careful with writing to a file and reading back. This may work doing one off...

This may be a dumb question, but if all you're doing is writing the XML document to the file system, then why are you bothering to map it to an XML variable at all. Just leave it as a Document variable, and write the document to the file system.???Howardhttp://www.avoka.com