Please remove the BOM feature from Schematic Capture

[KevinA]

1. "So you are saying that you didn't prep your components" I used Sample 6, when I layout each component has all information included
2. "Then what's your problem with my asking to just remove the feature" You said it was broken, my opinion of placing a BOM into a schematic does not make the feature irrelevant, it is to say I feel doing so is a waste of time BUT with a small project for final deliverable documentation it would be practical for some.
3. "I don't want the BOM on a schematic; " So the fact that the Export and Place Table is in the same Objects/Bill of Material window is why you feel the functionality is broke? Someone asked for the ability to place the BOM into a table or the programmers wouldn't have wasted time doing it.
4. "That comment shows that you know nothing about programming." Certified Oracle Programmer/System Administer, Novell Certified, 3Comm, Microsoft, ESRI, etc,ect the list goes on and on with plenty of programming, before DOS there were mini's Data General, Digital PDP's, certified, we had to load the OS from paper tape using front panels. When I started there were 4 bit processors from Intel... of course I worked for Intel (Systems management programming and instructor for RDBMS training in Oracle/Microsoft SQL, SQL, Infobase)
5. "Big deal. so are mine" - I thought that was what Python was for.... Something that I've ask DT about integrating into their product, after push & shove.
6. "Save your juvenile attempts at sarcasm" - Let it go.
7. "BTW, it's ironic that you're whining (that's how it's spelled)" WINE as in the Unix/Mac windows emulator since those that have to use it are bitching all the time instead of dedicating a PC for PCB design. "an easy task like a properly associative BOM" I would use your "That comment shows that you know nothing about programming" but if you'll notice I try not to denigrate while pointing out what I feel is not a correct assumption, "broken".
Perhaps you could read: How to Make Friends: A Guide for Social Skills - When you communicate you seem to denigrate more than communicate, I for one do not appreciate being denigrated or you could say disrespected, the point of a forum is discussing issues not flaming users.

[xfer]

I'll reduce the issue to this; You claim to be an expert on programming, yet you claim that detecting and updating changes in the BOM's underlying data is complicated and time-intensive. Either you are lying about your programming skills and knowledge, or lying about how it would take a prohibitively long and inconvenient time to do. How long does it take when you insert the BOM table for the first time? Do you even notice any delay? No. Your argument is silly.

[mike_s]

Regard xfer's babbling critique - DT offers another option not yet mentioned; go elsewhere ! EXIT is a good starting point.
Mike

[nisha_gomes]

The BOM table has been broken forever, and it would be better to just remove it. It never reflects any changes that have been made to the schematic, so users can get in trouble by relying on it to be accurate. I would rather just know that I must create my own BOM manually than expect to have the BOM be an accurate representation of the current schematic.

I understand your frustration with the BOM feature in Schematic Capture. It can indeed be challenging when the BOM table doesn't accurately reflect the changes made to the schematic. Relying on an inaccurate BOM can cause confusion and potentially lead to errors in the design process.

While it might be frustrating, manually creating your own BOM can be a good approach to ensure accuracy. By taking control of the process and meticulously documenting the components and their specifications, you can have a more reliable BOM that aligns with the current schematic.

However, it's also worth considering providing feedback to the software developers about the issues you're experiencing with the BOM feature. They may be able to address the problem or provide alternative solutions in future updates. Your input can help improve the user experience and make the software more efficient and reliable for everyone.

In the meantime, continue to rely on your own careful documentation and best practices to ensure accuracy in your designs. With attention to detail and manual verification, you can maintain control over the BOM and minimize any potential discrepancies.

[mrshad]

Thank you for sharing your experience and insights on using the BOM feature. It's valuable to hear different perspectives and technical expertise in our community

[novarm44]

The main problem in Schematic BOM auto-update that it may be quite large and take several separate pages. Updating and realigning pages may be a problem, updating single table is not a problem and is implemented in PCB Layout BOM.

BTW: First DipTrace push and shove video has been already published: viewtopic.php?p=34193#p34193

[Flux]

If you don't like it don't use it. I export to Excel and drop in to a BOM that calculates other things I want and wouldn't expect this software to do for me.
I use the interactive html version. I use it to keep track of pcb assembly and I would give it a 2.5 out of 5. It could use some added functionality such as selection clearing all at once, column add and delete, selected component identification (highlight or change color).

[captaincringe]

GB Whatsapp Download 2024The BOM table has been broken forever, and it would be better to just remove it. It never reflects any changes that have been made to the schematic, so users can get in trouble by relying on it to be accurate. I would rather just know that I must create my own BOM manually than expect to have the BOM be an accurate representation of the current schematic.

Exactly, I also think that creating a BOM manually would be the best option ever. As the BOM table not working well then we could have to chance to make a proper BOM table for individual as per their needs. But there is a trouble, does someone know how to make this BOM table manually? Because we haven't made it before.