|
Home > Archive > MS Access data conversion > November 2005 > Exit error
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
|
|
| Gary D. 2005-09-27, 9:24 am |
| I have just converted an Access 97 mdb to Access 2003.
In my application I have a MainMenu form (using a modified switchboard).
The form has an Exit button to quit Access.
It uses the code;
Application.Quit acQuitPrompt (was Application.Quit acSaveYes in Access 97)
This always used to work just fine and apart from changing the option
"acSaveYes " to "acQuitPrompt " I have not changed anything else in the code.
However, when I click the Exit button I now get Error 91 (object not set...
etc.).
I have also tried changing Application.Quit acQuitPrompt to Dcmd.Quit but I
still get Error 91.
When the error occurs I cannot see the code to debug it because the database
does close down and exit, so it would appear to be working successfully.
Any ideas what might be causing this Error 91 problem?
| |
| Van T. Dinh 2005-10-03, 3:24 am |
| Since the exiting the database and quitting Access will trigger other
Events, you may need to trace the code and see what triggers the error. See
also the following article which may / may not be applicable to you:
http://support.microsoft.com/?id=287485
--
HTH
Van T. Dinh
MVP (Access)
"Gary D." <me@privacy.net> wrote in message
news:vhkij1pid003ps2
72a3kvj0d5ple1peqb7@
4ax.com...
>I have just converted an Access 97 mdb to Access 2003.
>
> In my application I have a MainMenu form (using a modified switchboard).
> The form has an Exit button to quit Access.
> It uses the code;
> Application.Quit acQuitPrompt (was Application.Quit acSaveYes in Access
> 97)
>
> This always used to work just fine and apart from changing the option
> "acSaveYes " to "acQuitPrompt " I have not changed anything else in the
> code.
>
> However, when I click the Exit button I now get Error 91 (object not
> set...
> etc.).
>
> I have also tried changing Application.Quit acQuitPrompt to Dcmd.Quit but
> I
> still get Error 91.
>
> When the error occurs I cannot see the code to debug it because the
> database
> does close down and exit, so it would appear to be working successfully.
>
> Any ideas what might be causing this Error 91 problem?
>
| |
| Bret Reid Jones 2005-11-08, 4:15 pm |
| bret
"Gary D." <me@privacy.net> wrote in message
news:vhkij1pid003ps2
72a3kvj0d5ple1peqb7@
4ax.com...
> I have just converted an Access 97 mdb to Access 2003.
>
> In my application I have a MainMenu form (using a modified switchboard).
> The form has an Exit button to quit Access.
> It uses the code;
> Application.Quit acQuitPrompt (was Application.Quit acSaveYes in Access
97)
>
> This always used to work just fine and apart from changing the option
> "acSaveYes " to "acQuitPrompt " I have not changed anything else in the
code.
>
> However, when I click the Exit button I now get Error 91 (object not
set...
> etc.).
>
> I have also tried changing Application.Quit acQuitPrompt to Dcmd.Quit but
I
> still get Error 91.
>
> When the error occurs I cannot see the code to debug it because the
database
> does close down and exit, so it would appear to be working successfully.
>
> Any ideas what might be causing this Error 91 problem?
>
|
|
|
|
|