hidden database window shows on exit

[mwilliams4]

I have a Front end that in the startup properties has "show database
window" unchecked.
The app opens up just fine, but when you close down, the database
window shows for a few seconds and then it exits.

Anyone experienced this, and what do I do to stop it.

[Allen Browne]

What version of Access is this?
And what service pack? (See Help | About.)

Does it make any difference if you uncheck the Windows in TaskBar box under
Tools | Options?

Does this happen if no other forms or reports are open at the time you exit?

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

<mw********@socal.rr.comwrote in message
news:4c**********************************@i12g2000 prf.googlegroups.com...

>I have a Front end that in the startup properties has "show database
window" unchecked.
The app opens up just fine, but when you close down, the database
window shows for a few seconds and then it exits.

Anyone experienced this, and what do I do to stop it.

[mwilliams4]

What version of Access is this?

2003

And what service pack? (See Help | About.)

none

Does it make any difference if you uncheck the Windows in TaskBar box under
Tools | Options?

no

Does this happen if no other forms or reports are open at the time you exit?

I closed all except the database window and hid it, and it did not pop
back up when closing.

I have a hidden form that I keep open tied to the BE recordset.
But I do need that to stay open.

Can I program events to the database window?

[mwilliams4]

Thanks!
I'll install the SP's and take a run at the code.
Do you recommend a sequential SP1-2-3 install or can I go directly to
SP3.

[Allen Browne]

See what MS has to say about installing it:
http://support.microsoft.com/kb/870924

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

<mw********@socal.rr.comwrote in message
news:e1**********************************@h11g2000 prf.googlegroups.com...

Thanks!
I'll install the SP's and take a run at the code.
Do you recommend a sequential SP1-2-3 install or can I go directly to
SP3.

[mwilliams4]

Ok, let me give you my operating scenario, I need some advice.

I work for a company that does not let users have any access to the
outside world.
We are behind a firewall and very few people even have permission to
get to the internet.
MS AD based LAN.

They do not allow MS updates, in the thought that they don't want 50
different versions out there, and they also do not want to take the
reponsibility to keep all of the machines updated. I'ts a strange
situation I know, but it's one that I fought the battles and lost, and
have several scars to show for it.

I have an app which I've been asked to put together, and I will be
around perpetually to maintain.
It is built using Access 2003.
The extra security of A2003 vs A2000 was a pain initially, but I've
gotten around the issues, like e-mailing with ClickYesPro. (we do some
e-mail marketing and may move to the FMS e-mailer at some point.)
The app is a pretty standard Secured MDE FE / MDB BE, with VBA code
behind the app.
No web stuff or fancy frills.

The users are pretty much mine and I do have control (I use that
loosely) over the local environment (they can't have different SP's
unless I install them.
The SP's for Office 2003 I have read, really clamp down on such things
as receiving Excel and Word docs via outlook.
That is an issue for us as we are getting and sending a ton of those
files daily as a part of our workflow, and I don't want to blow that
up, and take on responsibility for that, just to bring up the SP level
for Access.

What I really need to have some advice on is DO I really have to move
up from the base A2003 install at all?
I don't want to do them willy-nilly just because MS puts it out ther,
I really need justification to do so, and I need to know how it will
negatively affect the other apps Excel, Outlook and Word.
I need advice like "you HAVE to get SP1, SP2 not so much" or
similar.
I looked at the SP3 list and I don't see anything there that I need,
and I'm going to look at the other two lists as well.

Sorry this is so long, but I had to present the whole story.

Thanks in advance for your input.

[Allen Browne]

Perhaps someone else who has struggled with a similar corporate environment
can give you advice here.

My personal recollection is that the original release of A2003 was one of
the most stable initial releases of Access ever. SP1 and SP2 did fix some
minor things. They also destroyed some functionality (e.g. inter-op between
Access and Excel.) SP3 really messed up the inter-op stuff across the board
in Office 2003, and is of marginal use or actually of negative value
(depending on what you need.)

So my perception is that the SPs for A2003 are not as crucial as they are
for A2000 or A2007 where you're a self-styled martyr if you don't apply at
least SP1.

(I think I misunderstood your last post to mean, Must I apply SP1 before I
will be able to apply SP2, etc.)

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

<mw********@socal.rr.comwrote in message
news:76**********************************@d21g2000 prf.googlegroups.com...

Ok, let me give you my operating scenario, I need some advice.

I work for a company that does not let users have any access to the
outside world.
We are behind a firewall and very few people even have permission to
get to the internet.
MS AD based LAN.

They do not allow MS updates, in the thought that they don't want 50
different versions out there, and they also do not want to take the
reponsibility to keep all of the machines updated. I'ts a strange
situation I know, but it's one that I fought the battles and lost, and
have several scars to show for it.

I have an app which I've been asked to put together, and I will be
around perpetually to maintain.
It is built using Access 2003.
The extra security of A2003 vs A2000 was a pain initially, but I've
gotten around the issues, like e-mailing with ClickYesPro. (we do some
e-mail marketing and may move to the FMS e-mailer at some point.)
The app is a pretty standard Secured MDE FE / MDB BE, with VBA code
behind the app.
No web stuff or fancy frills.

The users are pretty much mine and I do have control (I use that
loosely) over the local environment (they can't have different SP's
unless I install them.
The SP's for Office 2003 I have read, really clamp down on such things
as receiving Excel and Word docs via outlook.
That is an issue for us as we are getting and sending a ton of those
files daily as a part of our workflow, and I don't want to blow that
up, and take on responsibility for that, just to bring up the SP level
for Access.

What I really need to have some advice on is DO I really have to move
up from the base A2003 install at all?
I don't want to do them willy-nilly just because MS puts it out ther,
I really need justification to do so, and I need to know how it will
negatively affect the other apps Excel, Outlook and Word.
I need advice like "you HAVE to get SP1, SP2 not so much" or
similar.
I looked at the SP3 list and I don't see anything there that I need,
and I'm going to look at the other two lists as well.

Sorry this is so long, but I had to present the whole story.

Thanks in advance for your input.

[The Frog]

Hi Guys,

Just read my way through this thread and had a flashback moment....
Too much coffee. Anyway, I had a similar problem in A97 in my
strangely controlled coroprate environment, and I never found out
exactly what was causing it. I did however find a way to alleviate the
problem (or so it seems).

What I did was to make a 'Exiting Application' form. This was supposed
to be the last thing the app uses before shutting down. Basically all
it did was splash on the screen for a few moments while some code ran
to make sure that all objects (in my case ado recordsets and
connection objects) were cleaned up, all forms closed (except this
one), and the app was basically standing there all by its lonesome. I
even put a little progress bar on the bottom so people could watch it
take place! When all that cleaning and closing was done, the last bit
of code closed / quit the app. That was it. Annoying to have to do,
but it did solve the issue.

Just thought that might help

Cheers

The Frog

[mwilliams4]

Where exactly do you put the close database events?

[mwilliams4]

Dr. Evil Laughs....
'destroy all objects'

But really...that would be awesome.
Someone, please have this nugget of information for us.

[mwilliams4]

Bump to see if someone has the Destroy All Objects code.