VB project being modified implicitly

[CraigB]

I have a signed VB project which is somehow being modified and thus the
signature is being discarded. I know the users aren't modifying the
code through the VBIDE and my project doesn't use VBE to modify itself,
so what other actions could mark a VB project as 'dirty'?

I know with excel removing worksheets has this affect but is there
anything similar in Word? Not that I think I'm doing like that. My best
guess is it's something to do with one of my forms but all you can
really do with forms is set properties, so again I can't think where
the problem might be occurring.

TIA

Craig

 

[Tony Jollans]

If your 'Forms' include ActiveX controls (from the Control Toolbox) that is
probably the cause. I don't know exactly how it works but such controls do
trigger the 'document contains macros' warning on opening unsigned documents
so it seems highly likely that changes to them will be marked in some way as
changes to the project. I think the reasoning behind it is that they present
a possible security threat - and flagging them up as macros is an easy
(though confusing to many users) way to highlight the fact.

 

[CraigB]

What sort of changes could trigger this though?
Surely changing the value of enabled property on a control can't
constitute as a change to control that's worth persisting.

This is also the first project I've seen this occur on and I'm not
doing anything particularly clever or different this time.

 

[Tony Jollans]

Well, this is all guesswork on my part but I suspect Word sees *any* change
as relevant - it doesn't categorize them in any way.