Forum Discussion

bertinofra's avatar
bertinofra
Copper Contributor
Feb 08, 2022

Access error 2450 impossible to find a subform "etc, etc, etc,"

Dear,

I developed a Access 2019cdatabase (bought on December 2021) and it working fine. now  I have problem with it. Returned ccess error 2450 impossible to find a subform "etc, etc, etc,". an I help me?

 

Regards

FB

access
  • George_Hepworth's avatar
    George_Hepworth
    Silver Contributor
    Feb 08, 2022

    bertinofra Unfortunately, that's not nearly enough information to offer any suggestions. WHERE and WHEN does this error appear? Describe the situation in terms of steps you take, not the outcome or results. That way it's more likely someone will be able to figure out what problem might be present.

     

    • bertinofra's avatar
      bertinofra
      Copper Contributor
      Feb 09, 2022
      HI, Thank you for your cooperation. When I develod the application it workin fine. Now , at open principal forms, it returned me 2450 error Impossibe to find a subform (it is present on principal form), but I cannot to control with code this subfolder.
  • suyashthomson's avatar
    suyashthomson
    Copper Contributor
    Feb 21, 2022

    Hi bertinofra 

     

    Here is the workaround that can manually fix this Runtime Error 2450 Cannot Find The Referenced Form Error:

    • Switch on your system and sign in as an administrator.
    • Hit the Start button then choose All Programs > Accessories > System Tools > and then go for the System Restore option.
    • In the fresh window, opt for the “Restore computer to an earlier time” option and then hit Next.
    • Select the most current systems to restore points from the “On this list, click a restore point” list, and then press Next.
    • Then press Next on the verification window.
    • Reboot the system when the restoration is ended.

    Thanks!

     

  • Vexen_C's avatar
    Vexen_C
    Copper Contributor
    Sep 28, 2024
    Unfortunately this error is notoriously buggy, and occurs in situations and code where it makes no sense. It's possible the error refers to /something else/ but most of the time it doesn't mean what the error title says. I've hit it many times over two decades, and almost never found a rational reason for it (and sometimes, it doesn't even permit a On Error catch). If it occurs consistently, the only way is to rework the code or general concept of the code to avoid having to use the kind of line that causes it (like using Forms(X).HasModule).