5 ms·
I know it's fun to beat up on people who use their software meant for summing accounting tables as simple databases, but really the alternatives in these small
by bane 14y ago
I know it's fun to beat up on people who use their software meant for summing accounting tables as simple databases, but really the alternatives in these small cases usually introduce so much friction to the user and require so much work to get up and running as to not be worth it.
Even worse, most of the "right" solutions eliminate the easy look at dozens of rows that a spreadsheet offers (letting the user do fast unconscious visual comparisons in their own data) vs. showing what's essentially one row out of some table at a time.
Sometimes a simple grid that users can quickly navigate around, enter stuff into and see all of is the best solution.
The problem is that we (the tech industry) seem to only offer two choices, do it a) the wrong Excel way b) do it the huge giant IT initiative way...
I bet there's huge money to be made in a simple spreadsheet-like user interface that can be setup with similar constraints as a database (field types, foreign key constraints etc). That's all it seems both sides really want.
- simcop2387 14y agoThis is actually something that Access did fairly well. If someone made a nice frontend like it to SQLite you'd end up with a magic bullet for this. Access did very well as a frontend but on the backend it was horrible and unreliable for anything non-trivial. I've actually been thinking about QT's QML for this since it would let you build the interface like access did and has bindings for SQLite. Might be worth doing some real work on rather than just thinking.
- thirdsun 14y agoIn addition to Access, FileMaker might be an alternative here. It's easy to learn, cross platform, has simple and approachable design tools, field types, relations, SQL connectivity and is hands down the best solution when it comes to getting results fast.
- jchavannes 14y agoWhen I used to be an "IT guy", everything had to be in Excel. I begged to switch to Access. Hell, I even built a few prototypes in Access in my free time to demonstrate how much better it would be (I was still a student). My point: Over time, I came to appreciate Excel and realize what an amazing program it is. It is accessible to pretty much anyone who knows how to use a computer, and at the same time can basically be used to create mini-programs. That's the reason you only have the two choices you mentioned: a) do it the wrong Excel way b) do it the huge giant IT initiative way Also, Excel does provide the ability for both the data type and foreign key constraints you mentioned.
- cubicle67 14y agoAlso, not many people realise, but you can build forms in Excel which makes data entry much nicer
- intended 14y agoMaybe there should be a book. Doing the wrong thing the right way - How to use Excel in ways it was never intended.
- epo 14y agoI am sceptical about your final sentence, are you talking about anything other than the broad brush data validation constraints provided by Excel? If so please give examples.
- jchavannes 14y agohttp://chandoo.org/wp/2010/11/01/mix-vlookup-with-data-validation-for-some-magic-vlookup-week/ http://chandoo.org/wp/2010/11/01/mix-vlookup-with-data-valid...
- NickNameNick 14y agoAnd then someone emails 'the' spreadsheet to someone else, and now you have 2 different versions and no rational way to reconcile them. neither is authoritative anymore, and one probaby calculates the average of a list of phone numbers. (actual example...) They're great up to a point, and that point is sharing. I'm actually surprised that google docs hasn't picked up more traction for that reason alone. sharing a google docs spreadsheet doesn't cause divergence.
- roel_v 14y ago"I bet there's huge money to be made in a simple spreadsheet-like user interface that can be setup with similar constraints as a database (field types, foreign key constraints etc)." That's exactly what Access does (and Filemaker and literally 1000's of other packages over the last 2 or 3 decades), and still 'real' computer people piss on them and the people using it. And they're too difficult for 'normal' people to use beyond flat tables and forms, so in the end you still end up with a single choking point of one person who knows how these 'applications' work. The Excel way is in may cases the right way, from a business POV, and the collateral damage here are the developers who have to deal with the quirks of such a workflow.
- TheCapn 14y agoCompanies are in the business of software now whether or not their direct business is making/selling software. Its worth it -most of the time- to have a technical expert on retainer much like they would a maintenance person for any other skilled task they have in times of need. If we're working in a computer age of technology you can either fight it and fall behind, try to do things, doing them wrong, and fall behind, or suck it up and hire professionals for doing jobs a professional should do. Sorry for the mini-rant. I'm working for a small company right now as "the software guy" because everyone else here doesn't care about keeping things efficient. I don't blame them, they have their jobs to do and dealing with software sides of things for 2 hours every day isn't ideal nor appealing. But when you have a software expert on staff and you refuse to take his recommendations don't come crying to him when your half-baked workaround backfired. Maybe the point I'm aiming to make is developing database systems that are full featured yet still usable by people who can't mentally wrangle data and storage is a lost cause. I know we aim to empower users with their data but at times things become too vast and too important for a person without formal experience in large databases to "get their hands dirty" at the risk of blowing everything up.
- patrickk 14y agoSee also: YC request for startups, #22... "22. A web-based Excel/database hybrid. People often use Excel as a lightweight database. I suspect there's an opportunity to create the program such users wish existed, and that there are new things you could do if it were web-based. Like make it easier to get data into it, through forms or scraping. Don't make it feel like a database. That frightens people. The question to ask is: how much can I let people do without defining structure? You want the database equivalent of a language that makes its easy to keep data in linked lists. (Which means you probably want to write it in one.)" http://ycombinator.com/ideas.html http://ycombinator.com/ideas.html
- DanBC 14y agoThat's a good idea, but it's a bit scary. I've seen people use spreadsheets as word processors. They don't know how to layout a document in a word processor, but this spreadsheet lets them put words wherever they want. Sometimes people misuse spreadsheets. I guess it'd be really good to have some kind of transition from spreadsheets to more suitable tools. (Perhaps using spreadsheets as examples an metaphors?) This doesn't have to be software, it could be a short course on a website.
- sachingulaya 14y agoI know an accountant who knew how to use word processors but preferred to write essays in Excel. It's definitely peculiar.
- e12e 14y agoI'm still sad dabbledb.com folded up and went to work for twitter: http://www.youtube.com/watch?v=MCVj5RZOqwY http://www.youtube.com/watch?v=MCVj5RZOqwY
- MortenK 14y agoI just started a customer on Smartsheet.com, it is actually more or less exactly the above. There's webforms for data submission, special column types (contact dropdown lists, checkboxes etc). It's been running for a few weeks only, but so far its been a joy to use compared to the myriad of Excel files that were used before.
- kahawe 14y agoI think the problem isn't one or two people deciding to manage some 50 lines in an Excel file. The huge problem is that Excel file eventually growing and you start adding sheets and macros until it becomes this HUGE clusterfuck that some interns worked on too and other people who are long gone and folks are still using this monstrosity because that's "how we always did it"... and they continue to live with this broken crutch instead of re-doing it the right way at that point. I have seen user access reviews done in Excel, for way over 1000 users with an average of 8 accounts per user and at least 60 different managers who were responsible for checking their own employees and partly they would delegate it down to the individual team leaders. In one Excel file they sent around by email(!) and some poor sap who had to somehow make sense of it all and merge it.
- kyllo 14y agoThe problem is that we (the tech industry) seem to only offer two choices, do it a) the wrong Excel way b) do it the huge giant IT initiative way... And even when b) is chosen, when users log into the multi-million dollar CRM system, the first thing they reach for is still the "export to Excel" button. I see it as a failure of education. I have no CS background and when I was starting out at my first job, I would love to have known then what I know now about databases and database-driven application programming. I would love to have had a proper class or two about it in school. But I didn't, so all I knew was the bad, wrong, "e-mail the spreadsheet" way. At my old company we had people whose entire job was basically to take a huge Excel file, turn it into a pivot table (basically a simple cross-tab query) and e-mail the result to people periodically. I love Access forever because it sucked me into programming. I heard that it was a database but I didn't know what that meant and didn't have anyone who could teach me, so I learned it just by poking at it when I was bored at work until it started to make sense. Then I used it to mash two customer data sources together and tie a sales lead tracker to it--basically a quick and dirty replacement for our slow, over-engineered Oracle CRM system that no one actually used. I know now that what I made was also wrong in many ways and would make a real developer recoil in horror, but it was great fun to make and people actually used it. And it got me interested in databases, which got me into making LAMP apps, which got me into Rails, and so on...