[AccessD] Option Groups in continuous forms break SQL Execute: (MULTI-ROW FETCH)?

[Ryan W]

Hit send too soon. 

If unset the option groups control source , set the subform recordsource and then set the option group controlsource again the traces are a lot less chatty as well.  I’m using this continuous form on a tab control and changing the data between 4 sets of “grouped records” dynamically. 

Doing the above gets rid of most the chatter switching tabs except the initial load or switching the index to an entirely different PK. 



Sent from my iPhone

> On Feb 19, 2022, at 3:31 PM, Ryan W <wrwehler at gmail.com> wrote:
> 
> I suppose you’re right but it’s not like an option group is doing anything but applying a check or radio button based on the option value, so why would this control alone cause efficient multirow fetching to vanish? Enumerating a columns data doesn’t seem like a good enough reason. 
> 
> 
> 
> 
> 
> 
> 
> Sent from my iPhone
> 
>> On Feb 19, 2022, at 2:53 PM, Jim Dettman via AccessD <accessd at databaseadvisors.com> wrote:
>> 
>> 
>> I don't know that I'd call this a bug right off.
>> 
>> It just may be the nature of the beast.  There are a number of conditions
>> that cause single row fetches rather than multi-row, and that's been true
>> since Access 2.0 
>> 
>> This may be another one of those situations where it occurs and the reason
>> why it does is just not obvious right off.
>> 
>> Jim.
>> 
>> 
>> -----Original Message-----
>> From: AccessD On Behalf Of Ryan W
>> Sent: Friday, February 18, 2022 11:27 AM
>> To: Access Developers discussion and problem solving
>> <accessd at databaseadvisors.com>
>> Subject: [AccessD] Option Groups in continuous forms break SQL Execute:
>> (MULTI-ROW FETCH)?
>> 
>> Using an option group on a continuous form seems to use GOTO BOOKMARK when
>> opening/navigating instead of MULTI-ROW fetch.
>> 
>> You need to turn on Access SQL Tracing to really catch this but you can
>> also use SQL Profiler to see it's not preparing one statement for 10 rows
>> at a time, but preparing 10 separate statements:
>> 
>> This post is semi-related to early/late binding the rowsource/recordsource
>> bug here:.
>> 
>> https://codekabinett.com/rdumps.php?Lang=2&targetDoc=access-odbc-recordsourc
>> e-disables-multi-row-fetch-continuous-form
>> 
>> Similarly if you early bind the option group controlsource you will get
>> GOTO BOOKMARK lookups instead of one nice multi-row fetch. (late binding
>> fixes this, UNTIL the below occurs)
>> 
>> This then compounds itself when you use the continuous form in a subform
>> with a linkmaster/linkchild field relationship.. it completely breaks the
>> multi-row fetch even if you are late binding the option group control.
>> 
>> 
>> Shane if you see this can you get a confirmation on this?
>> -- 
>> AccessD mailing list
>> AccessD at databaseadvisors.com
>> https://databaseadvisors.com/mailman/listinfo/accessd
>> Website: http://www.databaseadvisors.com
>> 
>> -- 
>> AccessD mailing list
>> AccessD at databaseadvisors.com
>> https://databaseadvisors.com/mailman/listinfo/accessd
>> Website: http://www.databaseadvisors.com