Oracle在后面，Access在前面？
我“继承”了一个Access 2003项目。现在他们已经开始将我们升级到 2007 年。我是图腾柱上的低人（这是正确的），所以我无法访问 - 哈，没有双关语 - Big Mama Oracle 数据库，只能访问已在 Access 中另存为表（并内置到大量查询中）。
所以，为了让我了解一些非常基本的问题。
我从这次讨论中了解到，由于报告的复杂性，我应该从存储过程的角度进行思考。好的，我喜欢这个主意。这是很好的编程。
Access 07（显然）支持存储过程之类的东西（不是吗？）。然而，我读过一些关于它的可怕的事情，而且该部门的其他大部分还没有从 03 年升级。如果我在 07 年做我的工作，他们的 03 年将不知道如何处理我漂亮的存储过程，对吗？此外，如果事实证明 '07 确实不是该项目的正确选择（无论出于何种原因 - 谁知道，这对于该操作来说是新的），那么所有投入的时间都会立即过时。
由于 Big Mama 是 Oracle DB，因此显然必须稳定。那么，为什么我不直接研究一下 Oracle 中的 SP 呢？看起来这将产生最强大的应用程序：我知道我可以教 Access '03 和 '07 如何调用这些 Oracle SP。另外，我的编码将处于较低级别并更接近源代码，从而提高稳定性和效率。
我实际上可以在 Access '07（或 '03）中创建一个以 Oracle 为中心的 SP。我有点怀疑。
I "inherited" an Access 2003 project. Now they've begun upgrading us to 2007. I'm low man on the totem pole (and rightly so), so I don't have access - ha, no pun intended - to the Big Mama Oracle db, only the dumps that have been saved as tables (and built into a multitude of queries) in Access.
So, some very basic questions in order to get my bearings.
I learned from this discussion that, owing to the complexity of the reports, I should be thinking in terms of Stored Procedures. OK, I like that idea. It's good programming.
Access 07 supports (apparently), something like stored procedures (doesn't it?). However, I've read scary things about it, and much of the rest of the department has yet to upgrade from '03. If I do my work in '07, their '03's will not know what to do with my beautiful Stored Procedures, right? FURTHERMORE, if it turns out that '07 is really NOT the right choice for this project (for whatever reason -- who knows, it's new to this operation), then all the time invested is instantly obsolesced.
Since Big Mama IS an Oracle dB, clearly that's got to be stable. So, why don't I just wrap my head around SP's in Oracle? It seems like it would result in the most robust application for all: I'm given to understand that I can teach both Access '03 and '07 how to call those Oracle SP's. Plus, my coding will be lower level and closer to the source, which promotes stability and efficiency.
Can I actually create an Oracle-centric SP in Access '07 (or '03). I kinda doubt it.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
如果您在使用 Oracle 数据库支持的 Access 时遇到困难，我认为合理的做法是将尽可能多的工作转移给 Oracle。
这意味着，让 Oracle 来完成所有繁重的过程和函数（最好封装在包中）和视图。然后，使用 JDBC 允许 Access 仅查询并呈现结果。
这意味着学习 SQL 和 PL/SQL，但我认为这是值得的:)
If you're stuck using Access backed by an Oracle database, I reckon a reasonable path to follow would be to offload as much work to Oracle as possible.
That means, get Oracle to do all the heavy lifting with procedures and functions (preferably encapsulated in packages), and views. Then, use JDBC to allow Access to just query and present the results.
This means learning SQL and PL/SQL, but I think it's worth it :)