Distributing a pseudo web site on a CD -- easiest conversion process.

Our client has a web site with a catalog on it. User's viewing SQL data
through an ASP pick a category (say Sporting Goods) and go to the next ASP
to see data from another table (SQL), say a list of all sporting goods.
They then select the next level, say Baseball Bats and go to a product specific
ASP accessing and displaying data on all baseball bats.

Now we need to, essentially, "port" that entire functionality to a CD that
we will mail to customers. They will place the CD in their PC and, as long
as they have Windows 98 or better, they should be able to immediately see
and do exactly what they would have seen and done had they logged on to our
web site.

For reasons of cosmetic similarity and a desire to maintain only one system
(otherwise every subsequent cosmetic change to the web site would require
a code change on the CD version), we are considering using Data Access Pages
which I believe are new to Access 2000. We are told we can move the SQL
data to Access tables and the ASP's to Data Access Pages quickly and easily
each time we need to make a new CD version.

1 remaining question pertains to the Data Access Pages process. We could
port our files to Access files easily enough but I'm told that Data Access
Pages use Microsoft Office Web Components. Does this mean our customer would
have to have Microsoft Office or would the Access 2000 distribution license
allow us to place them on the CD where they could be immediately used by
the CD software without going through any install on the customer's machine?

If those components are an issue, some of the potential solutions we have
heard so far include:
1. The Microsoft Office Web Components is a library that you can reference
in the Access project, and the Package and Deployment Wizard would include
it in the Access distribution program it creates. Thus the customer would
not need to have anything but Windows to run the CD just as if they were
looking at the web site. True?
2.Another rumor holds that the Access 2000 Northwind Database has it's own
copy of Microsoft Office Web Components and, for that reason, any Access
projects can include the components -- no problemo. True?