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

One of the mysteries of the universe.

Here is the structure of a (simple) form...as to understanding it,
well..that is entirely another matter <g>

Max

Version =19
VersionRequired =19
Checksum =1766917867
Begin Form
    AllowDesignChanges = NotDefault
    DefaultView =0
    RecordLocks =2
    TabularFamily =48
    PictureAlignment =2
    DatasheetGridlinesBehavior =3
    GridY =10
    Width =10658
    DatasheetFontHeight =9
    DatasheetFontWeight =700
    DatasheetGridlinesColor =12632256
    RecSrcDt = Begin
        0x941b5921ae85e340
    End
    DatasheetFontName ="Verdana"
    Begin
        Begin Section
            Height =4025
            BackColor =-2147483633
            Name ="Detail"
            GUID = Begin
                0xe61055b85f5b6b4aaa61db723ad0763b
            End
        End
    End
End




-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Jim Dettman
Sent: 11 February 2010 21:24
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Add-In Express 2009 for Office and .NET


 I don't know. It's a really odd number.  I don't understand either why they
could not drop the old controls while a form was being edited.

 Probably if we understood the structure of a form internally, we'd know the
reasons why<g>

Jim.

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Max Wanadoo
Sent: Thursday, February 11, 2010 4:11 PM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Add-In Express 2009 for Office and .NET

That doesn't make any sense. It is not as if it  is going to UNDO 754
changes!

Wonder what the  logic there was?

Max


-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Jim Dettman
Sent: 11 February 2010 20:47
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

-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com