Max Wanadoo
max.wanadoo at gmail.com
Fri Jan 15 11:14:50 CST 2010
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