Good idea, Bill.
Norbert- You could add a simple MsgBox to the Unload event procedure to find out if it fires when the X is clicked - I would bet that it works.
John Viescas, Author
Microsoft Access 2010 Inside Out
Microsoft Access 2007 Inside Out
Microsoft Access 2003 Inside Out
Building Microsoft Access Applications
SQL Queries for Mere Mortals
(Paris, France)
On Dec 12, 2014, at 5:40 PM, wrmosca@comcast.net [MS_Access_Professionals] <MS_Access_Professionals@yahoogroups.com> wrote:
One thing you can do that might help you find the cause is to save the form as text and upload it here so the rest of us can take a look at it. To save as a text file, open the Immediate window by pressing Ctrl+G. Then type this in that window and press enter.
---In MS_Access_Professionals@yahoogroups.com, <drnorbert@msn.com> wrote :
SaveAsText acform, "yourFormName", "fullPathOfTextFileGoesHere"
Regards,
Bill Mosca, Founder - MS_Access_Professionals
Microsoft Office Access MVP
My nothing-to-do-with-Access blog
---In MS_Access_Professionals@yahoogroups.com, <drnorbert@msn.com> wrote :
John,
Is a complicated form which has four subforms (tab control) and 145 fields (I inherited this program I am stuck with this form by no choice for now) and when is in the loop CTRL+Break does not work.
I am not sure that the Form_Unload event will be activated if the loop is terminated by the X.
Any suggestions how to trace the cause of the loop?
By the way the program is designed in MSAccess 2013 which you mention before it is buggy.
Regards
Norbert
__._,_.___
Posted by: John Viescas <johnv@msn.com>
| Reply via web post | • | Reply to sender | • | Reply to group | • | Start a New Topic | • | Messages in this topic (9) |
.
__,_._,___
Tidak ada komentar:
Posting Komentar