A buch of traders got together and created a shared excel workbook to post pricing data for various forward curves. this spreadsheet grew and now it's 57mb and has over 25 users. As you may have surmised, this is causing severe performance problems and now it's my job to fix this problem.My thoughts were to remove the shared aspect of the workbook and replace it with a regular workbook calling a DLL that maintained the data in real-time across all the traders' spreadsheets from an Oracle DB. The data would be housed in a DB and disseminated via the DLL to all users. If two users simultaneously change data, the DLL would handle the deadlock by either taking the newest value or prompting the user for clarification.Now that I have that thought I was wondering if there are any alternate solutions I should consider. Is this possible (or easy) with C++ and .NET? Should I consider C#?Any help would be greatly appreciated.