[AccessD] [EXTERNAL] Re: Access lockup when using record selector search
shaneg at microsoft.com
Fri Mar 26 23:36:38 CDT 2021
The reason setting AllowAdditions to true makes a difference is that when it is set to true, then when the subform is first opened it has a single 'record' (the blank new record)
If it is set to false, then since the subform has no other records, so no records are displayed (and there is nowhere valid to put the focus in the form).
Getting the form open with no place to put the focus is one of the necessary conditions to hit this bug.
I will open an issue to track this. As always it is more likely we will fix a bug in Microsoft365, then it is that we will fix it in Access 2013 (or any of the perpetual license versions).
Thanks for providing a repro case Ryan.
From: AccessD <accessd-bounces+shaneg=microsoft.com at databaseadvisors.com> On Behalf Of Ryan W
Sent: Friday, March 26, 2021 3:51 PM
To: Access Developers discussion and problem solving <accessd at databaseadvisors.com>
Subject: [EXTERNAL] Re: [AccessD] Access lockup when using record selector search
This still doesn’t explain why .allowadditions = true or .allowdeletions = true seems to remedy the .refresh glitch without a requery... very odd indeed.
The underlying data isn’t changing on this form as the tables are local to the user and not linked to the back end.
Since you’ve seen the mock code that’s basically happening on my real FE. Moving data from BE to local table for processing.
Sent from my iPhone
> On Mar 26, 2021, at 5:45 PM, Stuart McLachlan <stuart at lexacorp.com.pg> wrote:
> Refresh method
> Use the Refresh method to immediately update the records in the
> underlying record source for a specified form or datasheet to reflect
> changes made to the data by you and other users in a multiuser
> environment. The Refresh method shows only changes that have been made
> to the current set of records; it doesn't reflect new records or deleted records in the record source.
> Requery method
> Use the Requery method to update the data underlying a form or control
> to reflect records that are new to or have been deleted from the record source since it was last requeried.
> If you want to requery a control that isn't on the active object, you
> must use this method, not the Requery action or its corresponding DoCmd.Requery method.
>> On 27 Mar 2021 at 8:40, Stuart McLachlan wrote:
>> There is a lot of confusion between Refresh and Requery.
> AccessD mailing list
> AccessD at databaseadvisors.com
AccessD mailing list
AccessD at databaseadvisors.com
More information about the AccessD