 Home |
 Content |
| Purchase |
| Ready-to-use samples |
| Online resources |
| Forum |
| Links |
| Happy readers |
Anonymous
Accessing Unsaved Documents / Unsaved changes to a Document (by Chris Jones, 05/17/2004 09:38:58 AM) |  |
Hi there folks,
First let me reiterate the praise for your book Normunds - there is nothing else like this anywhere - it's filled in gaps that other books avoid like the plague!
There may be a one word answer to this question, but hopefully someone can let me know if I am being stupid, or if I am right....
My question is: Am I right in thinking that you can't use the C API to access documents in memory? - let me give you my specific example:
I am developing a notes database where we perform some processing on the contents of a rich text field - the exact details of this are not really critical. Certain rich text elements are not supported (by design) and thus we need to parse the rich text before it is saved to make sure none of these elements are present.
With the help of this book, I have been able to write code in LotusScript that calls into the C API and returns a full read-out of the structure of the rich text field, so we can then prompt the user etc. when an element is not supported.
This is all fine, except that the only way I have been able to get this to work is to save the changes made to the document before parsing the rich text field, as my code won't work on a new document, or won't show any changes that have been made in the UI but not saved yet.
Is this just an instrinsic limitation of the C API? This does seem to be implied by the 'On Disk Structure' / ODS prefix. Is there a way to get a handle to a document in memory rather than on disk? and if so, will the ODS functions still work on it?
Any help in this area would be greatly appreciated...
Chris