Hi Stu,
What you're describing is not a requirement, but a partial solution. A
requirement is described in business terms. For example, your requirement
might be that you have information in Excel spreadsheets that you want to
display in a web site. Or it might be that you have Excel Spreadsheets that
you want users to be able to open and edit on your web site. Or it might be
that you have some data that you want to make available on your web site.
The first step to designing a solid solution is to have your requirements
spelled out well.
Now, it might seem picky of me to say all that, but there is a method to my
madness. For example, you didn't specify whether or not you want this
spreadsheet to be "read only" to your visitors. If it is meant to be edited,
putting an Excel spreadsheet onto a web page is going to be a real challenge
to an experienced programmer. On the other hand, if it is not supposed to be
edited, there are a number of much simpler solutions. However, embedding an
Excel spreadsheet in a web page isn't easy, and you may not even need to do
that, if, for example, your only requirement is that the data in it be made
available on your web.
So, what are your business requirements?
--
HTH,
Kevin Spencer
..Net Developer
Microsoft MVP
Big things are made up
of lots of little things.