Query Properties not sticking

[Perceptus]

I am trying to edit the properties for an Access 2007 query. I am trying to set the Subdatasheet name. I can use the drop down to select objects to use or type them in. When I press enter or leave the property field in the designer, the field goes back to being blank.



I am the only user in the database.

WHen i move the cursor to any of the properties the field appears to go blank, but when i change the focus to another property the field then shows what it is saved to. I have created an animated gif to show what is going on.


what is this madness?

[June7]

Does this issue happen for all queries? Does this happen in other dbs?

[Perceptus]

I saw it happening across the board and decided to reboot. Now everything is working like I had expected. Still kinda concerned how this occured from just sitting idle over the weekend.

[orange]

Just curious -- how did you do this

I have created an animated gif to show what is going on.

[Missinglinq]

...When I press enter or leave the property field in the designer, the field goes back to being blank...

...when i change the focus to another property the field then shows what it is saved to...

This has been documented often, as of 2007, vis-à-vis Properties of Forms/Forms Controls; I'm guessing that this has the same root cause, and to my knowledge has not yet been addressed by the Boys of Redmond. It has happened for so long that I automatically move to another Property after setting one, before leaving the Property Pane.

It's interesting to know that rebooting alleviates the problem, at least temporarily! Sounds sort of like Calculated Fields being blank, until they receive Focus, if the machine has been left up and running for an extended period of time!

Linq ;0)>

[Perceptus]

Also interesting how when I was typing into the field, the text appeared bigger than the normal text you see. Guess I will just power down over the weekend from now on.

[Missinglinq]

Well, you wouldn't let your car sit in the driveway, idling, for 60 hours...would you?

Linq ;0)>