
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