当你不是一名程序员时，你会在公司工作场所使用什么来代替 excel 呢？
我有一个朋友在一家没有真正 IT 人员的公司工作，他们采用了传统的公司路线，即在需要某些东西时就使用 Excel 宏将东西串在一起。我试图找出对于非程序员的人来说有哪些替代方案。
当您想要离线分发数据以及用于操作数据的表单时，有什么简单的 Excel 替代方案，并且没有陡峭的学习曲线？我本打算建议他学习 Python 和 SQL-lite，但我希望 StackOverflow 能给出更明智的答案。
I have a friend that is working on a company without any real IT people, and they've gone the classical corporate route of stringing things together with Excel macros whenever they need something. I was trying to figure out what alternatives are available for someone that isn't a programmer by trade.
What is an easy alternative to Excel when you want to distribute data offline together with forms for manipulating it, that doesn't have a steep learning curve? I was going to suggest he learn Python and SQL-lite, but I'm hoping StackOverflow can come up with a wiser answer.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
老实说，对于非开发人员（如果您内部没有开发人员）来说，Excel 确实没有任何问题。
话虽这么说，Lightswitch 对于数据工作的基本表单来说是一个新的且相当有趣的选项（尽管它仍然有点绿色）。
在我看来，一旦你走上了 Python 等语言的道路，你真的会看到一个必须成为程序员的人（他们可能经常搬起石头砸自己的脚）。
Honestly, for non developers (and if you do not have a dev staff in-house) there really isn't anything wrong with Excel.
That being said, Lightswitch is a new and fairly interesting option for basic forms over data work (although it's still a bit green).
IMO once you go down the route of languages like Python, etc. you're really looking at someone who is going to have to be a programmer (and they may be shooting themselves in the foot on a regular basis).
在这种类型的环境中，用户最终会使用 Excel 或 Access 来操作数据。 Excel 很方便，其中行中的单元格以相同的方式计算，但有特殊情况。 Access 更适合轻松计算多行、数据管理表单（是的 Excel 也可以做到，但 Access 更容易）和格式化报告。
在这种类型的环境中，我遇到的最佳情况是建立只读“数据仓库”，Excel 和 Access 用户可以从中链接或下载数据以自行操作。对于这种情况，SQL Server 可能是正确的选择，我在“数据仓库”周围使用引号，因为我并不是指技术意义上的它，而只是一个方便的存储库。这样您就拥有一个明确的记录系统。然后，在任一工具中生成的任何报告都会重复成为合并到该仓库中的候选者。
In that type of environment users end up with Excel or Access to manipulate data. Excel is convenient where cells in row are calculated the same way, but with exceptional cases. Access is better for calculating over multiple rows easily, data management forms (yes Excel can do it too, but Access is easier) and formatted reports.
The best situation I've arrived at in this type of environment is standing up read only "data warehouse" that Excel and Access users can link or download data from to manipulate on their own. For this situation SQL Server is probably the right choice and I use quotes around "data warehouse" because I don't mean it in the technical sense, but rather just a convenient repository. That way you have one definitive system of record. Then any report generated in either tool repeatedly becomes a candidate for incorporation into that warehouse.