Good practice

it depends. if that code will only be displayed on that page - of course
not. If it is dislpayed on multiple pages - perhaps.
"acidrain9" <webforumsuser@macromedia.com> wrote in message
news:el725l$b6r$1@forums.macromedia.com...
> There really isn't a problem... what i am asking is...
> Is it better to put the asp code for a recordset directly in my page code
> or should i put it in a separate file and include it in my page code?

There really isn't a problem... what i am asking is...
Is it better to put the asp code for a recordset directly in my page code or should i put it in a separate file and include it in my page code?

Not sure if I understand the nature of problem you are having.

Perhaps that you want to rephrase into one concise, clear question, one step at a time.

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?
>