MS-Access doesnt close

Hi guys,
Whenever i launch my app, use it and close it,
the MS-access insist in not finish. The app
ended but Ms-access keeps a windows opened.
Anyone knows this bug?? How to fix it??
Its MS-Access 2000.

Thank you all

Maffonso

re: MS-Access doesnt close

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

That was a recognized but in the earlier version of Access 2000. There
is a service pack (SP) that corrects that problem - see the Microsoft
download site.

In the mean time, one of the fixes was programmatic:

Some people use this True/False syntax:

If chkIsAllowed Then
...

If you used that syntax in your VBA change it to this:

If chkIsAllowed = True Then

Apparently, the bug happens when you don't use an explicit comparison
expression on a Boolean value.

--
MGFoster:::mgf00 <at> earthlink <decimal-point> net
Oakland, CA (USA)

-----BEGIN PGP SIGNATURE-----
Version: PGP for Personal Privacy 5.0
Charset: noconv

iQA/AwUBQdmbCoechKqOuFEgEQI80ACfTUaNIqfUbWm+RIoIujLkO2 KqMz8AoMBk
nnkNILFycJE2KZfP3VxCydnO
=Ev9+
-----END PGP SIGNATURE-----


maffonso@gbl.com.br wrote:[color=blue]
> Hi guys,
> Whenever i launch my app, use it and close it,
> the MS-access insist in not finish. The app
> ended but Ms-access keeps a windows opened.
> Anyone knows this bug?? How to fix it??
> Its MS-Access 2000.[/color]

re: MS-Access doesnt close

Also a known bug, if closing Access from code, always use DoCmd.Quit
instead of Application.Quit.
lq

re: MS-Access doesnt close

Also a known bug, if closing Access from code, always use DoCmd.Quit
instead of Application.Quit.
lq

re: MS-Access doesnt close

Also a known bug, if closing Access from code, always use DoCmd.Quit
instead of Application.Quit.
lq

re: MS-Access doesnt close

MGFoster wrote:[color=blue]
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> That was a recognized but in the earlier version of Access 2000. There
> is a service pack (SP) that corrects that problem - see the Microsoft
> download site.
>
> In the mean time, one of the fixes was programmatic:
>
> Some people use this True/False syntax:
>
> If chkIsAllowed Then
> ...
>
> If you used that syntax in your VBA change it to this:
>
> If chkIsAllowed = True Then
>
> Apparently, the bug happens when you don't use an explicit comparison
> expression on a Boolean value.
>[/color]

You may also use:

If chkIsAllowed.Value then


--
This sig left intentionally blank