Forum Discussion

RobM-BMT's avatar
RobM-BMT
Copper Contributor
Jun 23, 2023

Microsoft Access Version 2305 Build 16501.20210 breaks certain object access, returns null values

After the update to Microsoft Access a bit over a week ago (today is 6/23/23).  I can see from (https://learn.microsoft.com/en-us/officeupdates/update-history-microsoft365-apps-by-date) that Microsof...
access
Karl_Donaubauer's avatar
Karl_Donaubauer
MVP
Jun 23, 2023

Hi,

 

So far I have not seen any other reports of such a problem with this build.

Can you show a code example where the error occurs and provide the error number and the exact message?

Optimally, you could create a small sample database with the reproducible error and upload it somewhere. Then we could check it and if "successful" provide it to the Access team at Microsoft.

 

Servus
Karl
****************
Access Bug Trackers
Access News
Access DevCon

  • RobM-BMT's avatar
    RobM-BMT
    Copper Contributor
    Jun 23, 2023

    Karl_Donaubauer thank you for the response. Most of the data base works like it should but it is unusable with the errors we are getting. The first example listed below is an invalid use of null.

     

    The second example is an (action was cancelled) error. These errors occur in different parts of the program after hitting different buttons.

    The third example says method or data member not found.

     

    I hope this helps detail the problem.

    • Karl_Donaubauer's avatar
      Karl_Donaubauer
      MVP
      Jun 28, 2023

      Hi,

       

      It is difficult to figure out what is happening from a distance and from your examples, because they seem to have little to do with each other. In example 2, we don't see why opening the report is cancelled. That could e.g. be due to code in the open event.

       

      What strikes me about examples 1 and 3 is the way the field/control names are specified. I have sometimes seen and read that after some unknown change to Access installations or applications, referencing them as a property with the dot no longer worked. In these cases the error message in example 3 then was the usual one.

       

      You could try if it changes sth when you use this in example 1:

       

      Me!cbo_Cement_Name.Column(0)

      Me!txt_Cust_Name = Me!cbo_DeliveryID.Column(2)

      etc.

       

      i.e. always specify "Me" and replace the dots by bangs.

       

      You can try the same in example 3 and eventual code in the Open procedure of the report.

       

      Servus
      Karl
      ****************
      Access Bug Trackers
      Access News
      Access DevCon

Resources