A2K3 & object dependency refresh

Collapse
This topic is closed.
X
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • Darryl
    #1

    A2K3 & object dependency refresh

    I'm working on converting an A97 DB that someone else wrote to A2K3.

    It's converted fine, as far as I can see. Now while making changes,
    I've removed several buttons on a form that called reports, & removed
    the code that the buttons used; the reports are no longer needed.
    However, the object dependency view is still showing those reports
    linked to the form, even though I can't see anything that connects them
    any longer.

    Is there a way to do a complete refresh again of all object
    dependencies, similar to the analysis that ran when I first turned on
    Name AutoCorrect? If I can't trust the dependency listing, it won't be
    very useful.

    Tags: None
    • Br@dley
      #2
      Re: A2K3 & object dependency refresh

      Darryl wrote:[color=blue]
      > I'm working on converting an A97 DB that someone else wrote to A2K3.
      >
      > It's converted fine, as far as I can see. Now while making changes,
      > I've removed several buttons on a form that called reports, & removed
      > the code that the buttons used; the reports are no longer needed.
      > However, the object dependency view is still showing those reports
      > linked to the form, even though I can't see anything that connects
      > them any longer.
      >
      > Is there a way to do a complete refresh again of all object
      > dependencies, similar to the analysis that ran when I first turned on
      > Name AutoCorrect? If I can't trust the dependency listing, it won't
      > be very useful.[/color]

      Not sure, but you could try turning NameAutoCorrect off, compact, import
      all objects into new database or something? :)
      --
      regards,

      Bradley

      A Christian Response
      http://www.pastornet.net.au/response



        Comment

        • Allen Browne
          #3
          Re: A2K3 & object dependency refresh

          Darryl, try compacting the database, to get completely rid of the deleted
          form and its module.

          Personally, I have found the Object Dependency to be completely unworkable.
          I tried it on a database that was known to have queries that referred to
          tables that no longer existed, and forms/reports that used those tables. So
          I coded up some quick'n'dirty VBA to dump the dependencies to the immediate
          window. It constantly crashed Access (shut down by Windows repeatedly), and
          I never did get the code to run to completion.

          Not really surprising, since it's based on the woefuly unstable Name
          AutoCorrupt misfeature.

          --
          Allen Browne - Microsoft MVP. Perth, Western Australia.
          Tips for Access users - http://allenbrowne.com/tips.html
          Reply to group, rather than allenbrowne at mvps dot org.

          "Darryl" <DarrylJ@yahoo. com> wrote in message
          news:1135271287 .117310.124420@ f14g2000cwb.goo glegroups.com.. .[color=blue]
          > I'm working on converting an A97 DB that someone else wrote to A2K3.
          >
          > It's converted fine, as far as I can see. Now while making changes,
          > I've removed several buttons on a form that called reports, & removed
          > the code that the buttons used; the reports are no longer needed.
          > However, the object dependency view is still showing those reports
          > linked to the form, even though I can't see anything that connects them
          > any longer.
          >
          > Is there a way to do a complete refresh again of all object
          > dependencies, similar to the analysis that ran when I first turned on
          > Name AutoCorrect? If I can't trust the dependency listing, it won't be
          > very useful.[/color]


            Comment

            Previous template Next
            Working...