One ASP Page or Two?

Results 1 to 2 of 2

Thread: One ASP Page or Two?

  1. #1
    Join Date
    Dec 1969

    Default One ASP Page or Two?

    I'm having difficulty because I have a complicated asp page that can be used to enter new records into a DB but also edit them. You can edit them by finding the order, or you can edit them by seeing a list of orders and (in ASP Code, retreving them using Request.Querystring). I guess my question is, would it just be easier to make two asp pages. One for inserting new records and one for editing existing records. I know it's more work, but it would seem like it would be easier to keep things straight. Or should I just be using one asp page? Thanks in advance for the advice.

  2. #2
    Join Date
    Dec 1969

    Default RE: One ASP Page or Two?

    Personally...<BR><BR>I&#039;d say split it. ;-)<BR><BR>But others may argue.<BR><BR>Here&#039;s a compromise. Put all your common code into functions. Split the files and use SSIs to include your functions so that you don&#039;t have to code them twice.<BR><BR>Craig.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts