21–30 of 36 posts
I'm going to try it at work on Monday. If I like it, I'll buy it. You don't know how many times I've had to export a csv to do some sql on it, then import it back into excel.
Cheers
Feature Idea: Compile to "Vlookup" or compile to VBA. In other words: I build a spreadsheet with QueryCell, but I want people who don't have QueryCell to be able to use it. So I hit "Compile", and the program generates standard formulas using hlookup/vlookup and/or VBA so that the spreadsheet works for those who don't have the Plugin. (Of course it adds a link to "Built with QueryCell" :)
I don't quite follow though. To use querycell you load a normal Excel file into Excel. You can then open the QueryCell pane to query the regions of data in the open worksheet/workbooks.
The result sets returned from queries are then added to a new 'resultset' worksheet.
So as it stands you can pass around spreadsheets you have used with QueryCell to people without QueryCell.
Let me know if I misunderstand.
Cheers
You might want to get a professional PSD designer to sharpen the overall look. It has a template like look for design, though for this concept design might not be as important as selling it's functionality.
Good luck!
Feature Idea: Compile to "Vlookup" or compile to VBA. In other words: I build a spreadsheet with QueryCell, but I want people who don't have QueryCell to be able to use it. So I hit "Compile", and the program generates standard formulas using hlookup/vlookup and/or VBA so that the spreadsheet works for those who don't have the Plugin. (Of course it adds a link to "Built with QueryCell" :)
Thanks for the idea caffeine. I don't quite follow though. To use querycell you load a normal Excel file into Excel. You can then open the QueryCell pane to query the regions of data in the open worksheet/workbooks. The result sets returned from queries are then added to a new 'resultset' worksheet. So as it stands you can pass around spreadsheets you have used with QueryCell to people without QueryCell. Let me know…
It sounds like what you're doing is generating a new worksheet and populating it with (static) data generated by running the user's SQL query.
This is fine for sharing static data but b/c you're apparently not using excel formulas in generating the 'resultset' worksheet (it's just raw data, again) the 'resultset' sheets aren't going to be auto-updating if the underlying data got changed (on the 'sourcedata' worksheet, if you follow).
If you can compile SQL queries into excel formulas that'll stay updated as data change this goes from an A to A+ produce.
You should start by looking at the documentation for Vlookup and Hlookup, as those are the built-in functions people use to (fake) selection.
Congrats on the bold move. I am in the same boat -- just quit my job last Friday and will be working on my startup. I wish you the best of luck!
Alex
Earlier quoted context omitted.
I agree 100%, I don't think it is wise (at least initially) to water down your product with wizards, etc. Focus on that niche and focus hard.
Thanks for these opinions all. I can see the arguments both for and against wizards and gui query tools. On the one hand I personally agree with the jcdreads and viggity. These sorts of interfaces are very difficult to get right and dilute the SQL focus. On the other hand a number of people have suggested going this way, so people do think it would be useful. I have no immediate plans to go this way but I intend to b…
Earlier quoted context omitted.
Thanks for the idea caffeine. I don't quite follow though. To use querycell you load a normal Excel file into Excel. You can then open the QueryCell pane to query the regions of data in the open worksheet/workbooks. The result sets returned from queries are then added to a new 'resultset' worksheet. So as it stands you can pass around spreadsheets you have used with QueryCell to people without QueryCell. Let me know…
No offense but if you're not currently implementing this the way the guy suggested you can make the product a ton better if you take his suggestion (I'm guessing you yourself aren't a power user, again no offense intended). It sounds like what you're doing is generating a new worksheet and populating it with (static) data generated by running the user's SQL query. This is fine for sharing static data but b/c you're a…
Earlier quoted context omitted.
No offense but if you're not currently implementing this the way the guy suggested you can make the product a ton better if you take his suggestion (I'm guessing you yourself aren't a power user, again no offense intended). It sounds like what you're doing is generating a new worksheet and populating it with (static) data generated by running the user's SQL query. This is fine for sharing static data but b/c you're a…
Yep, exactly what I meant. Thanks for explaining it better.
I now understand what you is being suggested.
Yes it's true, that is not how QueryCell currently works.
I will have a think about this idea. My first impression is that it would be quite complicated to implement and get right but very powerful if done well.
Thanks Guys.