Baffling behaviour on Form close

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Petrol
    Contributor
    • Oct 2016
    • 285

    #16
    Just ran SFC.
    C:\Windows\Syst em32>sfc /verifyonly

    Beginning system scan. This process will take some time.

    Beginning verification phase of system scan.
    Verification 100% complete.

    Windows Resource Protection did not find any integrity violations.

    Comment

    • Petrol
      Contributor
      • Oct 2016
      • 285

      #17
      Just ran SFC:
      C:\Windows\Syst em32>sfc /verifyonly

      Beginning system scan. This process will take some time.

      Beginning verification phase of system scan.
      Verification 100% complete.

      Windows Resource Protection did not find any integrity violations.

      Comment

      • jimatqsi
        Moderator Top Contributor
        • Oct 2006
        • 1293

        #18
        Did you upgrade that machine from Access 32-bit to 64-bit?

        Comment

        • Petrol
          Contributor
          • Oct 2016
          • 285

          #19
          The computer was bought in December 2022 with 64 bit 365, and the Access application was recompiled for the 64 bit system.

          Comment

          • Gloryshine
            New Member
            • Jan 2025
            • 1

            #20
            The issue may stem from corruption in the Access database. Try these steps:
            1. Backup your database.
            2. Create a new database: Import all objects from the current database into a fresh .accdb file.
            3. Check references: Ensure all ActiveX and VBA references are valid and not missing.
            4. Review the subform relationship: Recheck the subform's record source and parent/child link properties for errors.
            5. Test on another device: See if the issue persists on a different computer.

            If the problem continues, a deeper file-level corruption may require a rebuild or use of a recovery tool.
            Last edited by NeoPa; Jan 4 '25, 01:32 PM. Reason: Removed potential for spam.

            Comment

            • Petrol
              Contributor
              • Oct 2016
              • 285

              #21
              Thank you, GLoryshine. If you check the history of this topic (especially posts #13 and #15 on 19 and 20 Srptember) you will see that the problem has been reproduced on a completely fresh database, so I have already tried your suggestions. Appreciate your thoughts, though.

              Comment

              Working...