Mojo
2009-05-09 19:39:31 UTC
Hi All
Apologies for the bizarre sounding subject text, but just wanted to put the
key factors in.
Basically I have a VB6 app that populates pre-created Word template docs and
everything is rosy on WinXP (all versions), but the same code on Vista does
the following:
1) Copy of Word template is populated and is displayed for user to look at
and if required they can save it to a diff filename. Thus the template is
never overwritten.
2) If the user doesn't want to save the doc and simply clicks the close box
then the usual 'Are you sure do you want to save' message box appears.
3) HOWEVER, upon closing this copy, a 2nd message box appears saying do you
want to save changes to the original template!!! Luckily the user has been
clicking No, but why is it doing this?
An example of one of my VB to Word 2000/2003 routines is as follows:
Set oWord = CreateObject("Word.Application")
Set oNewDoc = oWord.Documents.Add(App.Path & "\data\progress-inits.dot")
' = = = = = = = = = = = = = data goes in here
oWord.Visible = True
oWord.Activate
Set oDoc = Nothing
Set oNewDoc = Nothing
Set oWord = Nothing
Straightforward stuff don't you think?
Like I said, the routines work perfectly well in XP, but in Vista they
generate this anomaly.
Has anybody had this before? Is there a workaround?
Many thanks
Apologies for the bizarre sounding subject text, but just wanted to put the
key factors in.
Basically I have a VB6 app that populates pre-created Word template docs and
everything is rosy on WinXP (all versions), but the same code on Vista does
the following:
1) Copy of Word template is populated and is displayed for user to look at
and if required they can save it to a diff filename. Thus the template is
never overwritten.
2) If the user doesn't want to save the doc and simply clicks the close box
then the usual 'Are you sure do you want to save' message box appears.
3) HOWEVER, upon closing this copy, a 2nd message box appears saying do you
want to save changes to the original template!!! Luckily the user has been
clicking No, but why is it doing this?
An example of one of my VB to Word 2000/2003 routines is as follows:
Set oWord = CreateObject("Word.Application")
Set oNewDoc = oWord.Documents.Add(App.Path & "\data\progress-inits.dot")
' = = = = = = = = = = = = = data goes in here
oWord.Visible = True
oWord.Activate
Set oDoc = Nothing
Set oNewDoc = Nothing
Set oWord = Nothing
Straightforward stuff don't you think?
Like I said, the routines work perfectly well in XP, but in Vista they
generate this anomaly.
Has anybody had this before? Is there a workaround?
Many thanks