closing a db with an error

[kaosyeti@comcast.net via AccessMonster.com]

i have a db that i'm trying to finalized so i can get it out to 3 other
branch offices. when i was testing it, i found an error that i don't know
how to describe well, let alone fix. basically, i have one form that i use
to open all the other forms for the db. this one form, formlauncher, goes
visible=false every time another form opens, and in the closing codes of the
various other forms and reports is set to visible=true again. the problem is,
when one of the incidental forms is opened, and the program is closed (the
close button on access itself is clicked), it comes up with an error and
prompts you to either close or debug the code. no matter which option you
chose, it will close the whole program anyway. any ideas?

--
Message posted via AccessMonster.c om

http://www.accessmonster.com/Uwe/Forums.aspx/databases-ms-access/200512/1

[Br@dley]

Re: closing a db with an error

kaosyeti@comcas t.net via AccessMonster.c om wrote:[color=blue]
> i have a db that i'm trying to finalized so i can get it out to 3
> other
> branch offices. when i was testing it, i found an error that i don't
> know how to describe well, let alone fix. basically, i have one form
> that i use to open all the other forms for the db. this one form,
> formlauncher, goes visible=false every time another form opens, and
> in the closing codes of the various other forms and reports is set to
> visible=true again. the problem is, when one of the incidental forms
> is opened, and the program is closed (the close button on access
> itself is clicked), it comes up with an error and prompts you to
> either close or debug the code. no matter which option you chose, it
> will close the whole program anyway. any ideas?[/color]

Why not just close and reopen the form when needed?

Your code that runs when whatever form is closed must be causing the
problem. It would be helpful showing us the code.

You should have some error trapping code in it too. If you want to
"cludge" it put "On Error Resume Next" in the code (but that's bad
programming).
--
regards,

Bradley

A Christian Response

http://www.pastornet.net.au/response