[AccessD] Form Closing Problem - New(?)

Dan Waters dwaters at usinternet.com
Fri Jan 15 14:55:28 CST 2010


Hi Robert,

WXP SP3, Access 2003 SP3.  Customer uses the same.  

I don't know all the differences between their PC's and my PC - I have asked
them to let me know of any changes they've made in the last couple of days.

Dan

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Robert
Sent: Friday, January 15, 2010 2:50 PM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Form Closing Problem - New(?)

What are the specs here?? What OS are your customers using, What engine is
the program being run under on the customers computers, what are the
differences between your machine and thiers..?

Now that I'm developing in Windows 7, I have already found like 10 very very
strange issues cropping up in Access. As I can run the same EXACT program on
a Windows XP machine with no problems, but on a Windows 7 machine strange
problems...

WBR
Robert



-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Max Wanadoo
Sent: Friday, January 15, 2010 1:18 PM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Form Closing Problem - New(?)

Well,  you say "I doubt that", but, for example,  when I run my EatBloat
form to export all objects as  text, it prompts me to "do you want to save
Eatbloat" and do I want to save "mainmenu" forms before the export.  It does
this even though both forms are compiled,  compacted, etc and have
definitely not been changed.

Somehow, a flag gets unset on these two forms.  One has a timer  set to it,
the other does not. Apart from that I can see nothing out of the ordinary on
them.

So, maybe it is a  bug.

Best to create a new form and the copy-paste the controls into it and then
the code.

Max


-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Dan Waters
Sent: 15 January 2010 17:58
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Form Closing Problem - New(?)

Hi Max,

I do the same thing using a hidden form.  But on their system, they get
asked if they want to save the form BEFORE my hidden form's unload event is
fired.  

That's why this is difficult - between the time the user pushes the red 'X'
button on the Access window and when the unload event fires, Access asks if
an open form's design should be changed, and there is no code I can hook
into to investigate the problem.  The form's design doesn't change in form
view, only the underlying query for the form's data.

This has the behavior of a bug in Access, but I doubt that.

Dan

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Max Wanadoo
Sent: Friday, January 15, 2010 11:36 AM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Form Closing Problem - New(?)

Aha!  Well spotted.  Bet you're an analyst....

Can probably remove that as well - actually you can.  I do it all the time.
On my main-menu form I prevent that from closing until you click MY button
and that in  turn prevents Access from closing.

There we go....can't keep a good man down...LOL

Max


-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Heenan, Lambert
Sent: 15 January 2010 17:21
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Form Closing Problem - New(?)

He said "Access window's X button", not the Forms' X.

Lambert

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Max Wanadoo
Sent: Friday, January 15, 2010 12:15 PM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Form Closing Problem - New(?)

Sure you can. It is one of the options if the form's  properties.

Max


-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Dan Waters
Sent: 15 January 2010 16:27
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Form Closing Problem - New(?)

I don't think that I can remove the Access window's X button.  In any case,
all my customers want that X button, and the problem is only happening at
one customer, and not on my PC either.

Dan

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Max Wanadoo
Sent: Friday, January 15, 2010 9:36 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Form Closing Problem - New(?)

Dan, why not remove the X and force closure from the button.
Max


On 15/01/2010, RANDALL R ANTHONY <RRANTHON at sentara.com> wrote:
> Dan, I think you need...
>
> DoCmd.Close acForm, FormName, acSaveNo
>
>>>> On 1/15/2010 at 9:47 AM, in message 
>>>> <1E1D20B6B8184B2A8328033C3D0A775B at danwaters>, "Dan Waters"
>>>> <dwaters at usinternet.com> wrote:
> At only one customer, they are experiencing a problem when closing forms.
>
> For example, I can open a form in Form View add a new record.  If I 
> then close Access with the X button in the upper right corner of the 
> Access Window, Access now asks if they would like to save the changes 
> to the
form.
> This happens with forms after the recordset has been modified.
>
> If I close the form with a button that uses DoCmd.Close acForm, 
> Me.Name, then no problem.  If I leave the form open, then push a 
> button on the main screen to use Application.Quit, then no problem.  
> But if I've opened a
form
> in form view, changed the recordset, then close with the upper right X 
> button of the Access window, I get the question 'do I want to save
changes'.
>
> I've decompiled/compiled, compacted/repaired, and rebuilt the Access 
> files by importing all objects into a new Access .mdb file.  But that 
> doesn't help.
>
> Has anyone seen this issue?  How did you solve it?
>
> Thanks!
> Dan
>
>
>
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com (
http://www.databaseadvisors.com/
> )
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>
--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com

--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com

--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com

-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com

-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com

-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com

-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com


-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com




More information about the AccessD mailing list