Project and signature version compatibility

[kaldvelski]

I've come across some rather strange behaviour I'm hoping someone can
verify and hopefully suggest a solution to.

I've created a new document in Word 2003, then to the VB project added
an empty class module and finally signed the project with a digitial
signature.

I then open the document again using Word 2000 on a different machine
(i.e. one that doesn't have the certificate installed), dirty the
document in some manner and then save it.

If I save using Word's functions, Ctrl-S/Save button etc. it saves
fine.
If however I use ActiveDocument.Save then I get a message box about the
VB project being altered and my digital signature is stripped from the
project.

This is extremely irritating as it suggests I can't reuse the same
signed document across Word versions if I also want to use
ActiveDocument.Save - which I do. Could this be deliberate behaviour at
all.

More worryingly, I've also occasionlly noticed the VB project being
implicitly altered when using Word 2003 as well - a more complicated
project than the one described above though and it's not as consistent.
Which suggest the solution can't just be to have different document
version per version of Word.

I've been using certificates with my projects for a while - always with
templates rather than documents before however - and never seen
anything like this.

TIA

Craig

 

[Jezebel]

Merely dirtying the document content and saving is not affected by or
related to the signature, so File Save or ctrl-S should be firing any
signature messages. The signature relates specifically to the document's
VBA, and the correct behaviour is to remove the signature if the VBA
changes. If your 'activedocument.save' is in a macro that you've added, then
the behaviour is exactly what you should expect. If it's in the immediate
window, then that's more interesting: whether Word considers *any* activity
in the IDE to consistute a VBA change, I don't know.