Forums before death by AOL, social media and spammers... "We can't have nice things"
|    comp.lang.visual.basic    |    MS Visual Basic discussions, NOT dot-net    |    10,840 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 9,412 of 10,840    |
|    Dikkie Dik to Kevin Robinson    |
|    Re: VB6 DAO    |
|    13 Apr 05 12:54:54    |
      From: nospam@nospam.org              I never encountered this myself, but it seems that there are "hanging"       edits without updates or CancelEdits in some of your recordsets. If the       X button is clicked, some events are fired before the form is really       gone. It starts with the QueryUnload event that allows you to cancel the       closing, but if you don't want to cancel it is more clear to use the       Unload event of the form.              Best regards              Kevin Robinson schreef:       > Can anyone please help with a problem.       >       > My application uses an Access database and if I use my exit buttons setting       > db to nothing the database       > is closed down correctly.       >       > However if the X is used to exit at the top right hand corner of the form       > then a .idb file remains.       >       > How can I capture the X event so that I can ensure that the DB is closed       > down correctly?       >       >       > Thank in anticipation       >       > Kevin       >       >       >       >              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca