how to make changes in all the pages using asp

@sindhu_at — the fastest, safest way is to centralize the new table into one include file and then insert that include into every .asp page automatically. That builds on what @zippee, @Aykon and @VSBrown suggested but adds concrete, repeatable steps and quick automation so you don't edit 1000 files by hand.

Create a single include (for example /includes/mytable.inc) that contains only the table HTML. Verify it on a few pages in different folders by adding the include and viewing the page. The include directive looks like this:

<!--#include virtual="/includes/mytable.inc" -->

Automation workflow (test first on a copy):

1. Backup the site or use version control.
2. Manually add the include to three representative pages (different directories) and confirm layout and ASP behavior.
3. Use a bulk search-and-replace tool to insert the include before </body> (or wherever the table must go). Example Notepad++ regex find/replace:

Find: (?i)(</body>)
Replace: <!--#include virtual="/includes/mytable.inc" -->\r\n$1

Example PowerShell (run from repo root; test first):

Get-ChildItem -Recurse -Filter *.asp | ForEach-Object {
  $p = $_.FullName
  $t = Get-Content -Raw $p
  if ($t -notmatch "<!--#include.*mytable.inc") {
    $t = [regex]::Replace($t, "(?i)</body>", "<!--#include virtual='/includes/mytable.inc' -->`r`n</body>")
    Set-Content -Path $p -Value $t -Encoding UTF8
  }
}

Cautions and quick checks: use virtual when pages live in many folders (it’s root-relative); file is relative to the page. Server-side includes are resolved before ASP runs, and they must not be placed inside <% %> script blocks. Always test on a dev copy, watch for encoding/line-ending issues, and confirm in the browser by viewing page source. If editing files is impossible, the alternate (advanced) route is an IIS-level output filter or URL-rewrite module, but that adds complexity and should be a last resort.