Hi all,$version field is created in document when form-> versioning property is set. In my case i do not have this property set in form but few documents in the db have got $versionopt field with value 6. So i cannot edit these documents as editing creates new documents.
I would like to know how this field is set when i do not have it in my form.
Please help
-Arul
Subject: $versionopt in document but form versioning property not set
Hi ArulWhat is not clear from your post is that whether these are new documents or existing older ones? If they are old documents then maybe the form that these documents are created with was version enabled earlier and then it was taken out?
Subject: RE: $versionopt in document but form versioning property not set
Arshad,
Exact problem is, i have a mail-in db where documents are created from other db and mailed to this db. if i check the form property from where docs are created, it was not version enabled. but few of the docs in mail-in db has got this field. I am sure form property is not set. Some other way this field gets added to few documents and wondering how.
Subject: RE: $versionopt in document but form versioning property not set
We have the same problem with new copies being created in a mail in database. The documents arrive with $VerRef and $VersionOpt fields which are set when the documents are created using personal stationery. I haven’t been able to find the reason why these fields are set on personal stationery. They don’t appear to be in the form design and I haven’t found and preferences which the user can use to control this behaviour. Maybe, I haven’t looked far enough. As a workaround I am going to set up an agent to delete these fields when new mail arrives in the mail in database.
Subject: RE: $versionopt in document but form versioning property not set
Stationery is a stored document, not a design element. When you use Tools->New Memo - Using Stationery, you are actually opening the stored document for editing. One wouldn’t want to change the stationery every time one creates a message using the stationery, so the version option item is added (in the ProcessStationery sub in the UIMemoDocument class in the CoreEmailClasses script library) to ensure that the new document is created as a version of the old one, but without the parent-child relationship we usually want with versioning.
Subject: RE: $versionopt in document but form versioning property not set
Thanks Stan!!! Finally found the reason.