[AccessD] Add-In Express 2009 for Office and .NET

AFAIK, that will create a new form with the counter initialised.

That's one of the things that EATBloat does do for you.

-- 
Stuart

On 11 Feb 2010 at 15:57, Rocky Smolin wrote:

> If you hit the limit can you export the form to a text file and then
> reimport it to reset the object counter?
> 
> R 
> 
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Jim Dettman
> Sent: Thursday, February 11, 2010 12:47 PM
> To: 'Access Developers discussion and problem solving'
> Subject: Re: [AccessD] Add-In Express 2009 for Office and .NET
> 
> Max,
> 
>   Access has a limit of creating 754 controls over the lifetime of a form.
> Once you hit that limit, that's it.  You need to re-create the form.
> 
> Jim. 
> 
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Max (MGA)
> Sent: Thursday, February 11, 2010 3:35 PM
> To: 'Access Developers discussion and problem solving'
> Subject: Re: [AccessD] Add-In Express 2009 for Office and .NET
> 
> > . It also reset the lifetime control count,
> 
> What is this Ken?
> 
> Max
> 
> 
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Kenneth Ismert
> Sent: 11 February 2010 20:28
> To: accessd at databaseadvisors.com
> Subject: Re: [AccessD] Add-In Express 2009 for Office and .NET
> 
> > > Shamil:
> > > What I plan to do is a "lightweight" version of "EatBloat" within 
> > > Access Developer Assistant add-in ... And it will need .NET 
> > > Framework 3.0/3.5 installed on target system.
> > >
> > Ken:
> > Just so I'm clear, are you going to automate the EatBloat function 
> > using only .NET, or will you be calling the existing VBA code from .NET?
> >
> > Shamil:
> > Just using .NET, Ken.
> >
> > A COM-Add-In developed using C# and "Add-In Express for Office and .NET"
> > ...
> >
> 
> That sounds like a good idea.
> 
> I bumped into the limitations of VBA when I developed an Access Rebuild
> application which rebuilt Forms and Reports control-by-control,
> property-by-property.
> 
> The motivation for this was a monster frontend (almost 40Mb in mde format)
> with persistent corruption problems that not even SaveAsText/LoadFromText
> could fix.
> 
> The program, while time-consuming to run, was remarkably effective in giving
> the frontend a 'new lease on life'. Several huge forms, with almost a decade
> of development history, could now be edited without aggressive bloat. It
> also reset the lifetime control count, which allowed extending forms which
> had long since run into this limit.
> 
> I often thought that redoing the code in C# or VB.NET would have allowed a
> lot of extra flexibility in handling the coding issues that arose when
> tackling this problem.
> 
> -Ken
> --
> 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
> 
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com