简单 CRUD 数据库应用程序中的层次结构类型
我想为简单的小型企业数据库构建一个简单的应用程序（可能在 MS Access 中）。我们有相当典型的实体——客户、联系人、工人、供应商、分包商。这些都是一些假设的父类的变体，例如人。是否值得尝试在此类应用程序使用的表格和表单中反映这种层次结构？我们该怎么做呢？主表的人与每个类别的扩展表相关吗？为具有某种扩展子表单的人提供的表单？或者只是忘记所有这些，并为每种特定类型的实体编写类似但不同的表单和表格？这绝对不值得大量的工作或火箭科学。我可以遵循任何标准解决方案来获得额外的收益吗？
I want to build a simple app (probably in MS Access) for a simple small-business database. We have fairly typical entities -- customer, contact, worker, supplier, sub-contractor. These are all variations of some hypothetical parent class, e.g. person. Is it worth it to try to reflect this hierarchy in the tables and forms used by such an app? How would we do that? Master table of people with extension tables for each category related to it? Form for people with some kind of sub-form for the extensions? Or just forget all that and code similar but different forms and tables for each specific kind of entity? This is definitely not worth major amount of work or rocket science. Any standard solution out there that I can follow to get a little extra bang for the buck?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
如果这是针对桌面应用程序..那么我最好的选择是 RocketFramework。
它是免费的、强大的库，足够坚固，甚至可以开发企业规模的系统..所以它对你来说很重要..
If this is for a desktop application.. then my best bet is on RocketFramework.
It is free great library solid enough to develop even an enterprise scale system.. so it is big YES for you..