Dan Waters
dwaters at usinternet.com
Sat Jun 6 12:29:46 CDT 2009
Hi John, I'm wondering about this approach. It seems that people often use this to try to solve problems in their database. If a database is having problems, then perhaps keeping the EatBloat.mdb as an external tool might be a good approach, since it won't be affected by whatever problems might exist. I reformatted the code yesterday - added white space and indented 4 instead of 2. I'm just so used to this that I can't read code otherwise. Of course I'm not looking through the eyes of a 20-year old either! Dan -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby Sent: Friday, June 05, 2009 9:59 PM To: Access Developers discussion and problem solving Subject: Re: [AccessD] Naming subform control causes page fault Dan, If we can figure out how to make it an add-in then we can pull the code out of the form and divide it into modules however it makes sense. This would allow referencing the correct libs out in the mda, and would make it available from any access application for export / import any object. I am going to work on that idea. John W. Colby www.ColbyConsulting.com Dan Waters wrote: > Hi John, > > Well - lots of user options - eh? > > It's all in a single form, so it would be hard to split up the tasks. I'll > take a shot at it to see how it works and how it might be made easier for a > user. I'm guessing that all I will do is make the selections simpler for a > user. > > Dan > -----Original Message----- > From: accessd-bounces at databaseadvisors.com > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby > Sent: Friday, June 05, 2009 2:16 PM > To: Access Developers discussion and problem solving > Subject: Re: [AccessD] Naming subform control causes page fault > > I'm in if you want the help. > > John W. Colby > www.ColbyConsulting.com > > > Dan Waters wrote: >> OK - I'll give this a try. I like making utility programs - no guarantee > on >> when though! >> >> Send this to me at dwaters at usinternet.com. >> >> Thanks! >> Dan >> >> -----Original Message----- >> From: accessd-bounces at databaseadvisors.com >> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Max Wanadoo >> Sent: Friday, June 05, 2009 1:42 PM >> To: 'Access Developers discussion and problem solving' >> Subject: Re: [AccessD] Naming subform control causes page fault >> >> yes >> >> Max >> >> >> >> -----Original Message----- >> From: accessd-bounces at databaseadvisors.com >> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Dan Waters >> Sent: 05 June 2009 19:39 >> To: 'Access Developers discussion and problem solving' >> Subject: Re: [AccessD] Naming subform control causes page fault >> >> Max - do you mean a rewrite of EatBloat? >> >> Dan >> >> -----Original Message----- >> From: accessd-bounces at databaseadvisors.com >> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Max Wanadoo >> Sent: Friday, June 05, 2009 1:34 PM >> To: 'Access Developers discussion and problem solving' >> Subject: Re: [AccessD] Naming subform control causes page fault >> >> It could really do with a re-write though....any volunteers? >> >> Max >> >> >> >> -----Original Message----- >> From: accessd-bounces at databaseadvisors.com >> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of William Hindman >> Sent: 05 June 2009 19:19 >> To: Access Developers discussion and problem solving >> Subject: Re: [AccessD] Naming subform control causes page fault >> >> ...before you go that route you might give max's EatBloat a shot > ...whenever >> decompile fails to clear a strange behavior problem, I've found running > the >> mdb through EatBloat often cures what ails it ...its a pita until you get >> the sequence worked out but once there, its been a magic pill in my > arsenal. >> William >> >> -------------------------------------------------- >> From: "jwcolby" <jwcolby at colbyconsulting.com> >> Sent: Friday, June 05, 2009 11:21 AM >> To: "Access Developers discussion and problem solving" >> <accessd at databaseadvisors.com> >> Subject: Re: [AccessD] Naming subform control causes page fault >> >>> LOL, first thing I tried. The database is corrupted. A full on rebuild >>> is in order. >>> >>> John W. Colby >>> www.ColbyConsulting.com >>> >>> >>> Dan Waters wrote: >>>> Well - maybe it's time to drag out that old decompile shortcut! >>>> >>>> ;-) >>>> >>>> Dan >>>> >>>> -----Original Message----- >>>> From: accessd-bounces at databaseadvisors.com >>>> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby >>>> Sent: Friday, June 05, 2009 8:53 AM >>>> To: Access Developers discussion and problem solving >>>> Subject: [AccessD] Naming subform control causes page fault >>>> >>>> I have a pretty strange one at a client. They have a form with ~10 > tabs, >>>> each tab has one or more >>>> subforms. If I try and drag and drop a new subform onto a new tab > Access >>>> page faults when I try to >>>> save the subform. If I drag a new subform CONTROL onto the tab I can >>>> save >>>> it, but if I then try to >>>> name the subform control (change the name) it page faults when I try to >>>> save. >>>> >>> -- >>> 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