There's more, e.g. the SQLite engine can interact with Excel and fiddle with formatting, but I think the major thing is convenience. As a dev, most times I just wouldn't bother with the ODBC approach unless I really had to. Convenient C# and SQL though, I'd use them at least 10x more often.
Much of this functionality is available already, through ODBC, powershell, c# - but it's cumbersome to use. That's the selling point of this software, it seems to me.
Polish.
If it is the case, you did not even have to install it.
Dropbox did not only solve 'local file system'-mirroring, but (legal) file sharing in general.
Citations please.
"When Dropbox was getting off the ground in 2007, there were hundreds of small storage companies. It was almost a cliche, the way that many people believe mobile photo sharing is a cliche now, he says. “The important thing was, I would keep asking people if they used any one of these hundred options, and they all said no. These are my favorite problems to solve. You can’t focus on what everyone else is doing — it has to be about what’s really broken and what you can do to fix it.”"
http://firstround.com/review/How-to-Win-as-a-First-Time-Foun...
You can find when each of these companies were founded by following the links...
Don't remember the name, but I remember similar service even in late 90s, when dial-up was popular. You'd pay for some amount of storage hosted on their servers (no "cloud" term back then) and they had Windows client integrated as a drive. Not sure if they had "freemium", maybe dropbox differentiated with this business model.
https://stackoverflow.com/questions/15844633/using-excel-as-...
Once you create your ODBC source from the excel files, you can run queries and use the language of your choice (Python,C# ....). I am pretty sure you can also insert/update rows and columns too.
Wondering how this differs from the approach I describe (which has existed for many years).
Good work!