菜鸟寻求数据库帮助 [Access]
我对访问相当陌生，我不知道如何处理这种情况。我什至不知道从哪里开始所以任何帮助将不胜感激。
所以我必须设计这个数据库，其中包含诸如“音频板 X.xx”之类的项目。当客户订购“音频板 2.4”时，数据库将知道该板需要 2x4K 电阻器、4x2uf 电容器和 2X4401 BJT。在处理此订单时，它会自动从库存中提取它们，因此稍后我只需查看库存清单（比如在本周末），就会知道我需要订购哪些零件来重新进货。
现在，我在网上寻找帮助，我唯一能找到类似的东西是所谓的“材料清单”又名“BOM”表或其他东西......但他们都没有告诉我如何制作一个或类似的东西。
我对此真的很陌生，而且是个菜鸟。我正在使用 Access 2010。任何帮助将不胜感激。
I'm fairly new at access and I have no clue how to handle this situation. I dont even know where to start so any help would be greatly appreciated.
So I have to design this data base that has items such as "audio board X.xx" When a customer orders lets say "audio board 2.4", the database will know that the board requires 2x4K Resisters and 4x2uf Capacitors and 2X4401 BJTs. And it would automatically pull them from the inventory when processing this order so later on I can just look at the inventory list lets say at the end of the week and will know what parts i would need to order to restock.
now, i looked for help online, the only thing i could find similar was something called "Bill of Materials" AKA "BOM" sheets or something... but none of them told me how to make one or anything like that.
I'm really new at this, and am a total noob. I'm using Access 2010. Any Help would be appreciated.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
首先，阅读 http://r937.com/relational.html
您将需要按照以下方式进行设计：
零件
ID -->主键
描述
等等
组件
ID -->主键
描述
等等
PartsComponents -->接线表
零件 ID ---) ??
ComponentID ---)
如果一个部件只能拥有每个部件中的一个，那么生活就足够简单了，PartID + ComponentID 是您的主键，如果一个部件只能拥有一组特定部件，则可能可以将设置为单个项目，如果该零件可以具有可变数量的组件，则事情会变得有点复杂。不过，连接表中的数量字段可能会起作用。
然后，您将拥有一组相当标准的客户和订单表，其中包括订单详细信息表，当客户选择零件时，该表会通过附加查询从连接表信息中更新。
First, read http://r937.com/relational.html
You will need a design on the lines of:
Parts
ID -->Primary key
Description
Etc
Components
ID -->Primary key
Description
Etc
PartsComponents --> Junction table
PartID ---) ??
ComponentID ---)
If a part can have only one of each component, life is simple enough and PartID + ComponentID is your primary key, if a part can only have a set number of a particular component, it may be possible to treat the set as a single item, if the part can have a variable number of a component, things get a little more complicated. A quantity field in the junction table would probably work, though.
You then have a fairly standard set of tables for customers and orders, including an order detail table, which gets updated by an append query from the junction table information when a customer selects a part.