A form constantly asks to be saved whenever any changes are made to VBA in other forms

[EL_Gringo]

Late but...
Thanks to all for trying to help. To Pat, yes, I did both. As well, I created a new, blank database, imported all elements and relinked by hand to the BE. Same problem. I give up now, as the problem is annoying, but not lethal to my app.
I'm now facing a new problem which IS lethal. It has to do with running the app on machines with an Access language other than English. I'll post separately.
Again, thank you all for your time and effort.

 

[Pat Hartman]

You never posted enough of the app for us to find the error for you. Good luck.

 

[The_Doc_Man]

Update 2: After substituting the offending code - at least what I thought it to be - from all subforms on the main form, the app now constantly asks for the main form to be saved whenever I change code in other, unrelated forms.
It seems there is a deeper problem.
I checked the System Objects (SELECT MSysObjects.Name, MSysObjects.Type FROM MSysObjects and found more than 350 (!) Type 5, queries, all starting with '~sq_'. However, my application has only one saved query, and some of these '~sq_' are even from a totally different application (which as well has only one saved query). I did not use this other app as a starter for this one, and the other app does not have this problem.
I do have both apps open at the same time and am wondering if that could cause a problem.

Normally, those things that start with "~sq_" are dynamically created control queries for forms or reports that have, for example, .RowSource objects. Do you have any dynamically created or dynamically modified row source objects?

 

[EL_Gringo]

I have several forms with VBA. Whenever I make changes to VBA in one of them, a specific form asks to be saved, even though no changes have been made to its VBA. I tried compact and repair database and decompile, no success.

Last update and problem solved

Thank all of you for trying to solve this and for the other good advice. And I'm truly sorry to report back only now.

The devil is in the detail: In fact, one of the subforms manipulated a value in a textbox of the main form. I have no idea why that should trigger the 'has changed' of the main form, but it did. I have other forms with subforms doing the same without this phenomenon, but after erasing the offending line, the problem disappeared.