[AccessD] Possible Bug? Access 365 Version 2302 (Build 16130.20218)

[Ryan W]

I've gotten wind that this is a known bug that MS is aware of.  Sure wish
they'd be more transparent... hadn't seen anyone else mention it prior to
me bringing it up.  *shrug*

On Tue, Mar 7, 2023 at 8:38 AM Ryan W <wrwehler at gmail.com> wrote:

> I did some rollback testing. It appears thus far only the newest Office
> 365 update (16130.20218) is affected:
>
>
> Feb 28 - Version 2302 (Build 16130.20218) - **affected**
> Feb 14 - Version 2301 (Build 16026.20200) - unaffected
> Jan 26 - Version 2301 (Build 16026.20146) - unaffected
> Jan 10 - Version 2212 (Build 15928.20216) - unaffected
> Jan 4 - Version 2212 (Build 15928.20198) - unaffected
>
> On Tue, Mar 7, 2023 at 8:06 AM Ryan W <wrwehler at gmail.com> wrote:
>
>> Apologies for the multiple emails... working on this to get a feel for
>> what's going on
>>
>>
>> Here's a link to a basic 1 table / 1 query /1 form mdb that reproduces
>> the glitch:
>>
>>
>> https://drive.google.com/file/d/1VktXsLHAoeqeDL67eTukhYYVjVjRpF3O/view?usp=sharing
>>
>>
>> Another note: using the runtime simulation flag from the command line,
>> the subform now shows NO data but you can still click in / around to get
>> the query designer elements.
>>
>>
>>
>> On Tue, Mar 7, 2023 at 7:54 AM Ryan W <wrwehler at gmail.com> wrote:
>>
>>> Here's a short video of the glitch in action:
>>>
>>>
>>> https://www.screencast.com/t/dfLDfEE1B
>>>
>>> I've tried setting the subform control to locked = yes/enabled = no to
>>> no avail.
>>>
>>>
>>> On Tue, Mar 7, 2023 at 7:44 AM Ryan W <wrwehler at gmail.com> wrote:
>>>
>>>> I've got a form with a subform that has a stored query as a source
>>>> object.
>>>>
>>>> When I cursor over the data, I get what appears to be some of the query
>>>> design elements:
>>>>
>>>> Here is the "show" checkbox
>>>> https://i.imgur.com/rTniQct.png
>>>>
>>>> Crosstab pulldown:
>>>> https://i.imgur.com/5FUwo1w.png
>>>>
>>>> Total pulldown:
>>>> https://i.imgur.com/vJUR0vx.png
>>>>
>>>> I thought maybe it was some form corruption so I tried making a new
>>>> form with a subform referencing the same stored query and got the same
>>>> result?
>>>>
>>>> It also does this with stored queries that are NOT crosstabs (like the
>>>> above example)
>>>>
>>>>
>>>>