But now, you'd have a scalable infrastructure that could easily incorporate other sources of data -- both structured and unstructured -- into a comprehensive enterprise repository. In SharePoint 2010, a list can contain not just text and numbers, but also multimedia elements including audio and video, Office 2010 documents, and other binary objects.
Out of the box, a SharePoint installation includes blogs, wikis, team workspaces and document libraries. You can set item-level permissions, enable employees to check documents in or out, and have the ability to retrieve previous versions of documents for auditing and revision control. From within Office 2010, your users would be able to create their own lists and store their own documents online, your department managers could create their own sites, and your IT department can deploy new site collections as needed. Although moving that first list to SharePoint may take significant effort, building successive lists and sites gets easier and easier.
Furthermore, because the underlying data is being stored on the enterprise server farm instead of on an isolated PC, you can easily point external and mobile users to versions of shared data. You'd be able to create a parallel list containing just the data elements that you want to make public. That list would be contained within a site collection on an externally-facing web server, tapping into the shared database server on the enterprise server farm.
However, this transition from the private intranet to the public internet does require an upgrade to SharePoint Server 2010. There's only so far you can go with the free version of SharePoint, and if you're truly taking an ECM (enterprise content management) approach you'll hit the limits soon enough (see the comparison chart for details).