Booby Trapped Forms! Why?!

[Najemikon]

This isn't a request for help as such, just inviting comments on a very annoying situation that happens from time to time.

I have an application that I steadily develop, but once in a while after I've done some editing somewhere, an entirely unrelated form will fail. For instance, a subform will be blank, or won't find data it was happily displaying only a moment before.

After much stress and trauma, I always end up finding it is nothing to do with my edits, and couldn't be more simple than the forms properties (relating to data filters and rights) have changed. Not even to defaults though, and seemingly at random.

The most common is 'Data Entry' gets changed to "Yes", meaning it can't show existing records. Hence errors if my code is trying to show one record in particular. Todays, and the catalyst for this message, was much worse. All the data properties were set to "No"! No filters, additions, edits, deletions or data entry. Basically my form was reduced to a grey box...

Why can this happen? Why does Access see fit to booby trap my application?

 

[straybullet]

No answer unfortunately - but VERY grateful to see Im not imagining things when this happens!!! Thank you!

Let them hate - so long as they fear... Lucius Accius

 

[Najemikon]

That's a good answer actually. You imply that you're in the same position as me, which means it's less likely to be my fault!

 

[Crowley16]

I've never noticed this happening, not even for a single property...

is there some code in your db somewhere that steps through the controls collections or something?

--------------------
Procrastinate Now!

 

[Najemikon]

Nope. I frequently lock down particular fields using VBA to affect the visible, enable or lock properties, depending on what's applicable. These never alter except when they are supposed to.

I use VBA commands like 'Docmd.openform "frmName",,, acNewRecord' (sic), but I usually specify that the form is Data Entry anyway & it isn't used elsewhere. Again, never had a problem with these forms.

It's normally when I use VBA to open a subform & display a particular record, based on the parent form. I get an error, because somehow Data Entry is set to true. A property I would never touch on purpose, or via other VBA code.

And what messes with my sanity is the fact that I haven't even edited them so much as even changing the size when it happens! But something must trigger it. If I don't touch any part of my application ever again, I bet it would never happen.

It can't be another user either. It is a workgroup protected, shared (via Terminal Server) app, but I roll out an MDE file for the natives, while I use the MDB. Both point at the same backend.