Too much code behind form??? 
Author Message
 Too much code behind form???

Wow! That's amazing.
You should break up the code behind the form into Global Modules.
The controls problem is probably related to the lifetime maximum of 750
controls per form.
So if you add 500 controls, delete 300 and then add 300, you have exceeded
the lifetime maximum of 750.
You need to build a new form and cut and paste controls.
--
HTH
Joe
(Remove nospam from my e-mail address)

Quote:
> Is it possible to have too much code behind the form?  I have a very
complex
> and powerful form that we are using for In-House use.  I wouldn't build
> something like this for a client, but for us its very usfull like this.  I
> have over 5,600 lines of code behind the form and probably 150 to 200
> controls spread accross 6 or more tabs.  I would move some of the code
into
> seperate class modules, but the 5,600 lines of code is mostly UI type of
> code managing the UI.  The form does use about 10 class modules to manage
> the busisiness rules and logic, one of which has over 3700 lines of code.
> All in all there is almost 14000 lines for code used for this form.  My
> problem is:

> I.  can no longer save the control tab order on some of the tab pages
where
> there are lots of controls.  It seems that access can't manage that many
> controls.

> 2.  The code does not compile very well.  Where an un-declared variable
> would usually error during compile, it now doesn't error until the code
runs
> and hits that line of code or procedure.  It does some other buggy things
> but that's the most obvious one.

> have I pushed Access too far?

> --
> George Padvorac




Sun, 09 Sep 2001 03:00:00 GMT  
 Too much code behind form???
Is it possible to have too much code behind the form?  I have a very complex
and powerful form that we are using for In-House use.  I wouldn't build
something like this for a client, but for us its very usfull like this.  I
have over 5,600 lines of code behind the form and probably 150 to 200
controls spread accross 6 or more tabs.  I would move some of the code into
seperate class modules, but the 5,600 lines of code is mostly UI type of
code managing the UI.  The form does use about 10 class modules to manage
the busisiness rules and logic, one of which has over 3700 lines of code.
All in all there is almost 14000 lines for code used for this form.  My
problem is:

I.  can no longer save the control tab order on some of the tab pages where
there are lots of controls.  It seems that access can't manage that many
controls.

2.  The code does not compile very well.  Where an un-declared variable
would usually error during compile, it now doesn't error until the code runs
and hits that line of code or procedure.  It does some other buggy things
but that's the most obvious one.

have I pushed Access too far?

--
George Padvorac



Mon, 10 Sep 2001 03:00:00 GMT  
 
 [ 3 post ] 

 Relevant Pages 

1. Network Error - corrupted code behind form Access 2000

2. Modify query using code behind forms

3. Viewing Code Behind Forms: Unexpected Error

4. Progamatically Changing Code Behind Forms

5. Code-behind file inheriting from another code-behind file

6. Code Behind Forms Missing in A2K

7. Code behind forms or Modules - which is better?

8. Web Form & Window.Open in Code Behind

9. Passing Form Fields to VB.NET Custom Business Object in an ASP.NET Code Behind Page

10. How to set color coding w/o using code behind

11. How do I reuse code in the Code-Behind section of an ASPX page

12. Showing another form behind active form...

 

 
Powered by phpBB® Forum Software