John W. Colby
jwcolby at colbyconsulting.com
Mon Aug 15 14:21:57 CDT 2005
Well... In fact I may have found the culprit. I commented out all of the classes, including my framework form class and the crashing stopped. Slowly and painfully started uncommenting them one by one, testing each one about 25 times and found one class that seems to cause the crashing. I am continuing past that point, uncommenting all the rest one by one to see if I can get them all (except that one) back in without bringing the crash back. It's just painful, slow, piece by piece work. In the end Access shouldn't just close like it does, and it would be nice to actually get MS to find and fix the bug behind my bug, but I also have to be realistic... ;-) John W. Colby www.ColbyConsulting.com Contribute your unused CPU cycles to a good cause: http://folding.stanford.edu/ -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Gustav Brock Sent: Monday, August 15, 2005 2:56 PM To: accessd at databaseadvisors.com Subject: RE: [AccessD] Bug Report Hi John OK. I can count to "a dozen classes" times 20 and all the combinations of these 20 ... How about creating a macro to load the form 25 times and beep when unloading the form?? /gustav >>> jwcolby at colbyconsulting.com 08/15 8:18 pm >>> The size of the file is caused by the VB for all the controls. No, no graphics at all AFAIK. MAYBE a button... Hmmm I just looked at it and yea, I have graphics in the tabs - little pictures like can be found in buttons generated by the wizards. No pictures other than those. I will certainly take those out to see what happens. BTW, I went in and commented out all of the classes loaded by the form and the crashing has stopped. At least it looks like it. That is one of the problems, you can open the form 19 times and the 20th it will close the database. So every time you make a change you have to do a TON of searches (opening the form) before you are almost sure that you have managed to change the symptoms. John W. Colby www.ColbyConsulting.com Contribute your unused CPU cycles to a good cause: http://folding.stanford.edu/ -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Gustav Brock Sent: Monday, August 15, 2005 2:08 PM To: accessd at databaseadvisors.com Subject: RE: [AccessD] Bug Report Hi John But at 390K I guess your form contains some graphics - can't you skip that part? Also, if no code is run and the app still crashes, it looks like just the loading of the form causes the crash. The reason could be loading of graphics. Not likely, I know, but quick and easy to test. /gustav >>> jwcolby at colbyconsulting.com 08/15 7:30 pm >>> > Call SaveAsText(acForm, "tfrmClaim", "c:\tfrmClaim.txt") That was cool. The text file is 390 kbytes so it seems unliekly I can "scan it closely" And unfortunately, remember I said I had "pushed it out of the OnOpen" - the close is now back in the calling function that opens the form. The truly strange part is that there is no code left in that function, i.e. it just exits the sub. Sigh. I was going to try retyping in the offending line of code to see if I could clean the source stream. -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com