reserved error occured

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • Ronny Sigo

    reserved error occured

    Hello all,
    While develloping my application, at a certain point, a button which
    normally opens a form suddenly doesn't do so anymore. Instead I get a
    message which says:
    "A reserved error occured (-1517) There is no message available for this
    error" (Or at least something like this - cause I have the Dutch version)
    It came out of the blue, cause I did not change anything on the button nor
    the form which it's supposed to open.
    I haven't got the faintest idea what this is ... can anybody help me with
    this?
    Many thanks

    Ronny


  • Joan Wild

    #2
    Re: reserved error occured

    Ronny Sigo wrote:[color=blue]
    > "A reserved error occured (-1517) There is no message available for
    > this error" (Or at least something like this - cause I have the Dutch
    > version) It came out of the blue, cause I did not change anything on
    > the button nor the form which it's supposed to open.[/color]

    This error will occur if you change the design of a table, but don't follow
    through with a compact. If your database is split, it is a good idea to
    compact the backend after a design change, and also refresh the links in the
    frontend and compact it.

    --
    Joan Wild
    Microsoft Access MVP


    Comment

    • Ronny Sigo

      #3
      Re: reserved error occured

      Thanks Joan :)

      "Joan Wild" <jwild@nospamty enet.com> schreef in bericht
      news:1092dsilj0 82j5a@corp.supe rnews.com...[color=blue]
      > Ronny Sigo wrote:[color=green]
      > > "A reserved error occured (-1517) There is no message available for
      > > this error" (Or at least something like this - cause I have the Dutch
      > > version) It came out of the blue, cause I did not change anything on
      > > the button nor the form which it's supposed to open.[/color]
      >
      > This error will occur if you change the design of a table, but don't[/color]
      follow[color=blue]
      > through with a compact. If your database is split, it is a good idea to
      > compact the backend after a design change, and also refresh the links in[/color]
      the[color=blue]
      > frontend and compact it.
      >
      > --
      > Joan Wild
      > Microsoft Access MVP
      >
      >[/color]


      Comment

      Working...