@dbrownG4VN3: Trust me, you don't wanna go that way. Importing Excel in Revit is kinda useless, as you could only import cell data (raw data), no formulas, and only in some specific manner that Revit would understand. It is possible to create Revit schedules, export it to Excel, and create a bi-directional link between exported schedules and Revit data. Something like a Graitec extension or a CoBie extension. That would work.
Linking Excel as an OLE object in Revit doesn't seem very useful. The more Excel tables you link as OLE in Revit, the slower the Revit file will become. I do it all the time in Autocad, inserting dozen tables as OLE slows down Autocad file considerably and increases dwg size dramatically.
P.S. If you really need some text-based table (no formulas) in Revit, you can create a Revit schedule with some text parameters as instance parameters. Those parameteres would be like the columns in Excel. Then, you can give any text values to each instance for each row as you like.