#1   Report Post  
Posted to microsoft.public.word.docmanagement
AA2e72E AA2e72E is offline
external usenet poster
 
Posts: 17
Default Application.Version

Is there a (type of) field that will show application.version in a mail merge
document?
  #2   Report Post  
Posted to microsoft.public.word.docmanagement
Jezebel Jezebel is offline
external usenet poster
 
Posts: 1,384
Default Application.Version

Given that the application version can't change from run to run, why not
just type it in? But how on earth can it be relevant to the reader anyway?



"AA2e72E" wrote in message
news
Is there a (type of) field that will show application.version in a mail
merge
document?



  #3   Report Post  
Posted to microsoft.public.word.docmanagement
John McGhie [MVP - Word and Word Macintosh] John McGhie [MVP - Word and Word Macintosh] is offline
external usenet poster
 
Posts: 506
Default Application.Version

Yes: DocumentProperty (assuming you set the document property with the
correct string before you begin the mail merge).


On 24/8/06 8:57 PM, in article
, "AA2e72E"
wrote:

Is there a (type of) field that will show application.version in a mail merge
document?


--

Please reply to the newsgroup to maintain the thread. Please do not email
me unless I ask you to.

John McGhie
Microsoft MVP, Word and Word for Macintosh. Consultant Technical Writer
Sydney, Australia +61 (0) 4 1209 1410

  #4   Report Post  
Posted to microsoft.public.word.docmanagement
AA2e72E AA2e72E is offline
external usenet poster
 
Posts: 17
Default Application.Version

I think my question was specific enough? Why bother asking me why I want to
do that?

If you must know, I support a mail merge functionality within an application
that runs from a COM server, however, the documents are created from
individual PCs that run varios versions of Word from 97 onwards. The COM
Server has Word 2003.

In the event of errors, the first thing I need to know is what version of
Word created the mail merge document.

Using the DOC property is an unlikely answer as the document can be created
in one version and amended in another etc.
  #5   Report Post  
Posted to microsoft.public.word.docmanagement
Suzanne S. Barnhill Suzanne S. Barnhill is offline
external usenet poster
 
Posts: 33,624
Default Application.Version

So are you wanting the version in which it was originally created or the
version in which it was most recently edited? I believe the document
property will be the latter, but I'm not sure how this document property is
accessed; it is certainly displayed in the File Open dialog if you choose
the Properties view. I have documents that show Microsoft Word 6.0, Word for
Windows 95, Word 8.0, Word 10.0, and Microsoft Word Document (always the
current version, in this case Word 11.0). No 9.0 because I skipped Word
2000. It may be that VBA is required to extract this information.

--
Suzanne S. Barnhill
Microsoft MVP (Word)
Words into Type
Fairhope, Alabama USA
Word MVP FAQ site: http://word.mvps.org
Email cannot be acknowledged; please post all follow-ups to the newsgroup so
all may benefit.

"AA2e72E" wrote in message
...
I think my question was specific enough? Why bother asking me why I want

to
do that?

If you must know, I support a mail merge functionality within an

application
that runs from a COM server, however, the documents are created from
individual PCs that run varios versions of Word from 97 onwards. The COM
Server has Word 2003.

In the event of errors, the first thing I need to know is what version of
Word created the mail merge document.

Using the DOC property is an unlikely answer as the document can be

created
in one version and amended in another etc.




  #6   Report Post  
Posted to microsoft.public.word.docmanagement
Jezebel Jezebel is offline
external usenet poster
 
Posts: 1,384
Default Application.Version


I think my question was specific enough? Why bother asking me why I want to
do that?


Because a lot of posts fix on a preconceived method, when the underlying
problem, once understood, can be approached in some other way. In your case,
for example, it might be sufficient to identify the *computer* that created
the mailmerge document, and separately maintain a list of the computers and
what version of Word they are running. And if each computer has a standard
user, you could use the Author property to identify the machine ... This
mightn't be ideal, but it has the virtue of simplicity, and it's a solution
that's immediately available.


Using the DOC property is an unlikely answer as the document can be
created
in one version and amended in another etc.


Use an AutoNew function to define the property if you want to know the
original machine; use AutoOpen if you want to know which last amended it.

1. In your template, predefine a custom property called AppVersion. Assign a
dummy valye.

2. In the body of the template, use { DocProperty AppVersion } to display
the value.

3. In your code, use: ActiveDocument.CustomDocumentProperties("AppVersio n")
= Application.Version


  #7   Report Post  
Posted to microsoft.public.word.docmanagement
AA2e72E AA2e72E is offline
external usenet poster
 
Posts: 17
Default Application.Version

"Jezebel" wrote:

Because a lot of posts fix on a preconceived method ....


It is the document that I am interested in not the computer on which it was
created; I can see the document (saved in a database as a BLOB). Why would I
be interested in maintaining a table of computer names and their respective
versions of Word? If I rely on this, I am guaranteeing a wild goose chase for
sure as there is no way to ensure that the table is up to date except by
conducting an audit of all computers. In my case, the document can be created
by a client off-site and I have no way of getting to it ....
  #8   Report Post  
Posted to microsoft.public.word.docmanagement
Jezebel Jezebel is offline
external usenet poster
 
Posts: 1,384
Default Application.Version

You stated your objective as knowing what version of Word created the
document. Since that will be specific to each computer, knowing which
computer produced the document will tell you that.

But you seem happier herding dead horses.






"AA2e72E" wrote in message
...
"Jezebel" wrote:

Because a lot of posts fix on a preconceived method ....


It is the document that I am interested in not the computer on which it
was
created; I can see the document (saved in a database as a BLOB). Why would
I
be interested in maintaining a table of computer names and their
respective
versions of Word? If I rely on this, I am guaranteeing a wild goose chase
for
sure as there is no way to ensure that the table is up to date except by
conducting an audit of all computers. In my case, the document can be
created
by a client off-site and I have no way of getting to it ....



  #9   Report Post  
Posted to microsoft.public.word.docmanagement
AA2e72E AA2e72E is offline
external usenet poster
 
Posts: 17
Default Application.Version


"Suzanne S. Barnhill" wrote:

it is certainly displayed in the File Open dialog if you choose the Properties view


This might be usefull however, I am at a loss. Please detail the step by
step process for this.

To date I have explored the following:

1. Use the shell application to interrogate all the 40+ properties of the
document: I do not see the version of Word among these properties.
Incidentally, this includes the number of pages in the document as well as
the user who created it and the name of the computer on which it was done.
2. Use an auto macro to write Application.Version to a hidden bookmark, The
problem with this is that the macro needs to be in a template and I cannot
ensure that users not only use this template and also leave the hidden
bookmark intact.
3. Read bytes at the beginning if the file to see if the version is buried
in the I cannot see that it is (I do not have documentation of the
internal structure of Word documents).

  #10   Report Post  
Posted to microsoft.public.word.docmanagement
AA2e72E AA2e72E is offline
external usenet poster
 
Posts: 17
Default Application.Version



"Jezebel" wrote:

But you seem happier herding dead horses.


You are determined to miss the point: While I have access to the document, I
do NOT have accesss to EVERY computer that creates a document (to query its
version of Word) AND IT people do NOT tell me if they change/upgrade a
computer with a later version of Word or rebuild the computer with another
version.

Therefore I want to be able to establish the version Word from the document.




  #11   Report Post  
Posted to microsoft.public.word.docmanagement
Tony Jollans Tony Jollans is offline
external usenet poster
 
Posts: 1,308
Default Application.Version

I don't believe you can (easily) extract this information from within Word
but the name of the creating application is held in the Summary Information
property set, details he
http://msdn.microsoft.com/library/de...us/stg/stg/the
_summary_information_property_set.asp

--
Enjoy,
Tony

"AA2e72E" wrote in message
...

"Suzanne S. Barnhill" wrote:

it is certainly displayed in the File Open dialog if you choose the

Properties view

This might be usefull however, I am at a loss. Please detail the step by
step process for this.

To date I have explored the following:

1. Use the shell application to interrogate all the 40+ properties of the
document: I do not see the version of Word among these properties.
Incidentally, this includes the number of pages in the document as well as
the user who created it and the name of the computer on which it was done.
2. Use an auto macro to write Application.Version to a hidden bookmark,

The
problem with this is that the macro needs to be in a template and I cannot
ensure that users not only use this template and also leave the hidden
bookmark intact.
3. Read bytes at the beginning if the file to see if the version is buried
in the I cannot see that it is (I do not have documentation of the
internal structure of Word documents).



  #12   Report Post  
Posted to microsoft.public.word.docmanagement
AA2e72E AA2e72E is offline
external usenet poster
 
Posts: 17
Default Application.Version

Thanks for the link; looks hopeful. I'll try it out.

  #13   Report Post  
Posted to microsoft.public.word.docmanagement
John McGhie [MVP - Word and Word Macintosh] John McGhie [MVP - Word and Word Macintosh] is offline
external usenet poster
 
Posts: 506
Default Application.Version

That's what Jezebel was getting at :-)

No, you *don't* need to know the *application* version, you need the "File
Format". Check for Version "Word.Document.8" in the meta-data at the
bottom of the document.

I think you'll get that from the DSOfile.dll which is freely available on
the Internet.

There's no correspondence between Application Version and File Format (well,
there is, but anything more recent than Word 97 will write anything more
recent than Word.Document.1" version...)

Some new merge fields arrived with Word 2002, I believe. But generally, the
fields and their interpretations and encoding have remained unchanged since
Word 6 on the PC.

Cheers

On 25/8/06 3:19 AM, in article
, "AA2e72E"
wrote:

I think my question was specific enough? Why bother asking me why I want to
do that?

If you must know, I support a mail merge functionality within an application
that runs from a COM server, however, the documents are created from
individual PCs that run varios versions of Word from 97 onwards. The COM
Server has Word 2003.

In the event of errors, the first thing I need to know is what version of
Word created the mail merge document.

Using the DOC property is an unlikely answer as the document can be created
in one version and amended in another etc.


--

Please reply to the newsgroup to maintain the thread. Please do not email
me unless I ask you to.

John McGhie
Microsoft MVP, Word and Word for Macintosh. Consultant Technical Writer
Sydney, Australia +61 (0) 4 1209 1410

Reply
Thread Tools
Display Modes

Posting Rules

Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT +1. The time now is 07:14 AM.

Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 Microsoft Office Word Forum - WordBanter.
The comments are property of their posters.
 

About Us

"It's about Microsoft Word"