title: Getting a handle on a huge classic asp project
body: <p>I've been working with an ASP Classic site with over 500 files, some of which aren't used and some of which are; along with a database with hundreds of procs and functions and tables, in the same shape.</p>
  
  <p>I need a way to get a grip on the project so I can eventually migrate it. I don't have time yet to walk through every single page and look at the SQL (stored procedures are in the database and are called properly within the ASP pages), so I'm at a loss as to how to get a handle on this.</p>
  
  <p>My immediate thought is to make ASP classes and put them into the pages as I go - they'd pretty much be used for getting and setting fields, validation, and sending recordsets into display functions.</p>
  
  <p>Is this a reasonable approach? Am I missing some strategy? </p>
  
  <p>How would you approach this? A migration to another platform at this point is considered, but not feasible for the short term (next couple of months)</p>