Access XP strange behaviour

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • Sebastian C.

    #1

    Access XP strange behaviour

    Hello everybody

    Since I upgraded my Office XP Professional to SP3 I got strange
    behaviour.
    Pieces of code which works for 3 years now are suddenly stop to work
    properly.
    I have Office XP Developer (SP3 for Office, SP1 for developer,
    JET40SP8) on Windows XP Home Edition (SP1). The same behaviour occurs
    on Windows 98 too.

    1. The DoMenuItem don`t work anymore as it works until a couple a
    weeks. When I try to delete a record using following code
    (DoCmd.DoMenuIt em acFormBar, acEditMenu, 8, , acMenuVer70
    DoCmd.DoMenuIte m acFormBar, acEditMenu, 6, ,
    acMenuVer70 )
    I got the error message 3021 "No current record". This code works fine
    in Access 97 and in Access 2000 ( I have them installed on the same
    box with Access XP) but it stops working properly in Access XP.
    2 . Also when I`m trying to delete a record, error message 3709 "The
    search key was not found in any record" appears.

    Does anyone know why this strange behaviour occurs and if there is a
    solution to these problems?

    Thank you very much for your time!

    Sebastian C.
  • Allen Browne

    #2
    Re: Access XP strange behaviour

    This is a known issue with Office XP SP3.

    Just add error handling to the routine to ignore error 3021.
    The delete works, and it sorts itself out after this event is over.

    --
    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.

    "Sebastian C." <sebastic@xnet. ro> wrote in message
    news:9959a732.0 406301138.c6da2 4d@posting.goog le.com...[color=blue]
    > Hello everybody
    >
    > Since I upgraded my Office XP Professional to SP3 I got strange
    > behaviour.
    > Pieces of code which works for 3 years now are suddenly stop to work
    > properly.
    > I have Office XP Developer (SP3 for Office, SP1 for developer,
    > JET40SP8) on Windows XP Home Edition (SP1). The same behaviour occurs
    > on Windows 98 too.
    >
    > 1. The DoMenuItem don`t work anymore as it works until a couple a
    > weeks. When I try to delete a record using following code
    > (DoCmd.DoMenuIt em acFormBar, acEditMenu, 8, , acMenuVer70
    > DoCmd.DoMenuIte m acFormBar, acEditMenu, 6, ,
    > acMenuVer70 )
    > I got the error message 3021 "No current record". This code works fine
    > in Access 97 and in Access 2000 ( I have them installed on the same
    > box with Access XP) but it stops working properly in Access XP.
    > 2 . Also when I`m trying to delete a record, error message 3709 "The
    > search key was not found in any record" appears.
    >
    > Does anyone know why this strange behaviour occurs and if there is a
    > solution to these problems?
    >
    > Thank you very much for your time!
    >
    > Sebastian C.[/color]


    Comment

    • Sebastian C.

      #3
      Re: Access XP strange behaviour

      "Allen Browne" <AllenBrowne@Se eSig.Invalid> wrote in message news:<40e38074$ 0$24741$5a62ac2 2@per-qv1-newsreader-01.iinet.net.au >...[color=blue]
      > This is a known issue with Office XP SP3.
      >
      > Just add error handling to the routine to ignore error 3021.
      > The delete works, and it sorts itself out after this event is over.
      >
      > --
      > 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.
      >
      > "Sebastian C." <sebastic@xnet. ro> wrote in message
      > news:9959a732.0 406301138.c6da2 4d@posting.goog le.com...[color=green]
      > > Hello everybody
      > >
      > > Since I upgraded my Office XP Professional to SP3 I got strange
      > > behaviour.
      > > Pieces of code which works for 3 years now are suddenly stop to work
      > > properly.
      > > I have Office XP Developer (SP3 for Office, SP1 for developer,
      > > JET40SP8) on Windows XP Home Edition (SP1). The same behaviour occurs
      > > on Windows 98 too.
      > >
      > > 1. The DoMenuItem don`t work anymore as it works until a couple a
      > > weeks. When I try to delete a record using following code
      > > (DoCmd.DoMenuIt em acFormBar, acEditMenu, 8, , acMenuVer70
      > > DoCmd.DoMenuIte m acFormBar, acEditMenu, 6, ,
      > > acMenuVer70 )
      > > I got the error message 3021 "No current record". This code works fine
      > > in Access 97 and in Access 2000 ( I have them installed on the same
      > > box with Access XP) but it stops working properly in Access XP.
      > > 2 . Also when I`m trying to delete a record, error message 3709 "The
      > > search key was not found in any record" appears.
      > >
      > > Does anyone know why this strange behaviour occurs and if there is a
      > > solution to these problems?
      > >
      > > Thank you very much for your time!
      > >
      > > Sebastian C.[/color][/color]



      Is the same issue with Office XP SP3 regarding the error:
      "3709. The search key was not found in any record." also when I try to
      delete a record?

      Thank you very much!

      Sebastian C.

      Comment

      • Allen Browne

        #4
        Re: Access XP strange behaviour

        Haven't seen Err 3709 caused by SP3. That message may indicate a corruption
        in the database.

        You might also check if this knowledgebase article applies:



        --
        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.[color=blue]
        >
        > Is the same issue with Office XP SP3 regarding the error:
        > "3709. The search key was not found in any record." also when I try to
        > delete a record?
        >
        > Thank you very much!
        >
        > Sebastian C.[/color]


        Comment

        Working...