A2K db crashes after A2K3/ADE installed

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

    A2K db crashes after A2K3/ADE installed

    I have just installed Office 2003 and Visual Studio Tools for Office 2003,
    including the Developer Extensions for Access. I kept my Access 2000/MOD
    installation intact (I hope), installed Access 2003 and upgraded all the
    other Office apps. I have all updates/service packs installed including Jet
    SP8. OS is XP Pro.

    I have a repeatable situation where opening a report with code will cause
    any mdb to crash every time. The following is one sample of code but ANY
    code that opens ANY report in ANY mdb results in a crash under the
    circumstances described below:

    Dim stDocName As String
    Dim boolSubs As Boolean

    Me.Refresh
    boolSubs = Me.Check55
    DoCmd.Close

    If boolSubs = True Then
    stDocName = "rptWindows 1"
    Else
    stDocName = "rptNoSubTo tal"
    End If

    DoCmd.OpenRepor t stDocName, acPreview

    Nothing too exotic here.

    These are the steps that put the mdb in a state where the above code crashes
    the app:

    1.Open the mdb in Access 2003, compile under 2003 - code runs fine. Close
    mdb

    2.Open same mdb with Access 2000 after it has been compiled under 2003,
    attempt to open report and Access crashes. Every time. Recompiling under
    2000 either before or after trying open report does not help. Once its broke
    recompiling doesn't fix it. Opening reports directly from the database
    window does not cause the crash.

    The only variation is sometimes just opening in 2003 then opening a report
    with code in 2000 is enough to cause the crash. Compiling under 2003 causes
    the problem every time but just opening with 2003 sometimes causes the mdb
    to crash when subsequetly opening a report in 2000.

    I see a description of my symptoms in an NG where the solution was to update
    printer drivers. If that's the problem why would using code to preview a
    report cause a crash while previewing from the db window doesn't?

    I have tried this with several different mdbs, all developed under 2000 and
    get the same results. So far it seems Access 2003 is harder to live with
    than previous versions, but it always seems like that at first.

    Anyone have similar experiences or comments?

    Thanks for any comments or help.

    Brent


    Tags: None
    • Brent
      #2
      Re: A2K db crashes after A2K3/ADE installed

      Further:

      I uninstalled Office 2003 leaving Access 2000 on the machine by itself. All
      the 2000 mdbs now work without error or problem.

      Copied those mdbs to another machine that has only Office 2003 installed.
      Opened, ran, compiled without error or problem.

      Copied mdbs compiled on Office 2003 machine back to Access 2000 machine.
      They still work fine; run, open reports, etc without error or problem.

      So....Access 2003 and 2000 can't live on the same machine?

      Brent
      "Brent" <brento@telus_N O_SP_AM_planet. net> wrote in message
      news:hA_cc.2050 6$J56.15528@edt nps89...[color=blue]
      > I have just installed Office 2003 and Visual Studio Tools for Office 2003,
      > including the Developer Extensions for Access. I kept my Access 2000/MOD
      > installation intact (I hope), installed Access 2003 and upgraded all the
      > other Office apps. I have all updates/service packs installed including[/color]
      Jet[color=blue]
      > SP8. OS is XP Pro.
      >
      > I have a repeatable situation where opening a report with code will cause
      > any mdb to crash every time. The following is one sample of code but ANY
      > code that opens ANY report in ANY mdb results in a crash under the
      > circumstances described below:
      >
      > Dim stDocName As String
      > Dim boolSubs As Boolean
      >
      > Me.Refresh
      > boolSubs = Me.Check55
      > DoCmd.Close
      >
      > If boolSubs = True Then
      > stDocName = "rptWindows 1"
      > Else
      > stDocName = "rptNoSubTo tal"
      > End If
      >
      > DoCmd.OpenRepor t stDocName, acPreview
      >
      > Nothing too exotic here.
      >
      > These are the steps that put the mdb in a state where the above code[/color]
      crashes[color=blue]
      > the app:
      >
      > 1.Open the mdb in Access 2003, compile under 2003 - code runs fine. Close
      > mdb
      >
      > 2.Open same mdb with Access 2000 after it has been compiled under 2003,
      > attempt to open report and Access crashes. Every time. Recompiling under
      > 2000 either before or after trying open report does not help. Once its[/color]
      broke[color=blue]
      > recompiling doesn't fix it. Opening reports directly from the database
      > window does not cause the crash.
      >
      > The only variation is sometimes just opening in 2003 then opening a report
      > with code in 2000 is enough to cause the crash. Compiling under 2003[/color]
      causes[color=blue]
      > the problem every time but just opening with 2003 sometimes causes the mdb
      > to crash when subsequetly opening a report in 2000.
      >
      > I see a description of my symptoms in an NG where the solution was to[/color]
      update[color=blue]
      > printer drivers. If that's the problem why would using code to preview a
      > report cause a crash while previewing from the db window doesn't?
      >
      > I have tried this with several different mdbs, all developed under 2000[/color]
      and[color=blue]
      > get the same results. So far it seems Access 2003 is harder to live with
      > than previous versions, but it always seems like that at first.
      >
      > Anyone have similar experiences or comments?
      >
      > Thanks for any comments or help.
      >
      > Brent
      >
      >[/color]


        Comment

        • david epsom dot com dot au
          #3
          Re: A2K db crashes after A2K3/ADE installed

          > So....Access 2003 and 2000 can't live on the same machine?

          They can, normally. Either it's something new, or (more likely)
          you have just been unlucky.

          BTW, I once had an application that worked perfectly except
          that one feature I wanted was missing. I just thought it was
          designed that way. Later I found that my copy of the executable
          differed by ONE BYTE from the copy on the installation floppy.
          And installation has only become more complex since then....

          (david)

          "Brent" <brento@telus_N O_SP_AM_planet. net> wrote in message
          news:uo3dc.1487 4$Sh4.829@edtnp s84...[color=blue]
          > Further:
          >
          > I uninstalled Office 2003 leaving Access 2000 on the machine by itself.[/color]
          All[color=blue]
          > the 2000 mdbs now work without error or problem.
          >
          > Copied those mdbs to another machine that has only Office 2003 installed.
          > Opened, ran, compiled without error or problem.
          >
          > Copied mdbs compiled on Office 2003 machine back to Access 2000 machine.
          > They still work fine; run, open reports, etc without error or problem.
          >
          > So....Access 2003 and 2000 can't live on the same machine?
          >
          > Brent
          > "Brent" <brento@telus_N O_SP_AM_planet. net> wrote in message
          > news:hA_cc.2050 6$J56.15528@edt nps89...[color=green]
          > > I have just installed Office 2003 and Visual Studio Tools for Office[/color][/color]
          2003,[color=blue][color=green]
          > > including the Developer Extensions for Access. I kept my Access 2000/MOD
          > > installation intact (I hope), installed Access 2003 and upgraded all the
          > > other Office apps. I have all updates/service packs installed including[/color]
          > Jet[color=green]
          > > SP8. OS is XP Pro.
          > >
          > > I have a repeatable situation where opening a report with code will[/color][/color]
          cause[color=blue][color=green]
          > > any mdb to crash every time. The following is one sample of code but ANY
          > > code that opens ANY report in ANY mdb results in a crash under the
          > > circumstances described below:
          > >
          > > Dim stDocName As String
          > > Dim boolSubs As Boolean
          > >
          > > Me.Refresh
          > > boolSubs = Me.Check55
          > > DoCmd.Close
          > >
          > > If boolSubs = True Then
          > > stDocName = "rptWindows 1"
          > > Else
          > > stDocName = "rptNoSubTo tal"
          > > End If
          > >
          > > DoCmd.OpenRepor t stDocName, acPreview
          > >
          > > Nothing too exotic here.
          > >
          > > These are the steps that put the mdb in a state where the above code[/color]
          > crashes[color=green]
          > > the app:
          > >
          > > 1.Open the mdb in Access 2003, compile under 2003 - code runs fine.[/color][/color]
          Close[color=blue][color=green]
          > > mdb
          > >
          > > 2.Open same mdb with Access 2000 after it has been compiled under 2003,
          > > attempt to open report and Access crashes. Every time. Recompiling under
          > > 2000 either before or after trying open report does not help. Once its[/color]
          > broke[color=green]
          > > recompiling doesn't fix it. Opening reports directly from the database
          > > window does not cause the crash.
          > >
          > > The only variation is sometimes just opening in 2003 then opening a[/color][/color]
          report[color=blue][color=green]
          > > with code in 2000 is enough to cause the crash. Compiling under 2003[/color]
          > causes[color=green]
          > > the problem every time but just opening with 2003 sometimes causes the[/color][/color]
          mdb[color=blue][color=green]
          > > to crash when subsequetly opening a report in 2000.
          > >
          > > I see a description of my symptoms in an NG where the solution was to[/color]
          > update[color=green]
          > > printer drivers. If that's the problem why would using code to preview a
          > > report cause a crash while previewing from the db window doesn't?
          > >
          > > I have tried this with several different mdbs, all developed under 2000[/color]
          > and[color=green]
          > > get the same results. So far it seems Access 2003 is harder to live with
          > > than previous versions, but it always seems like that at first.
          > >
          > > Anyone have similar experiences or comments?
          > >
          > > Thanks for any comments or help.
          > >
          > > Brent
          > >
          > >[/color]
          >
          >[/color]


            Comment

            Previous template Next
            Working...