I have started to yank some of my recordset and include them
in common
files - I find it helps when I want to change the SQL and
don't want to do
it multiple times. For example, I have a news section that is
carried
through several sections of the site. By having it included
instead of "on"
every page, I can change it's content and appearance at one
place instead of
5.
In general, though, many pages and the subsequent SQl is
pretty specialized
to the page.
"acidrain9" <webforumsuser@macromedia.com> wrote in
message
news:el4o4l$g4f$1@forums.macromedia.com...
>i have noticed that after adding a few recordsets and
stored procedures
>that
> the code on some of my pages is getting really long...
my question is...
> is
> it ok that the code is getting longer or should i be
putting stored
> procedures
> and/or recordsets into separate files and include them
in the page?
> is anything gained or lost by either method?
>