Do you use the Excel BOM feature? 2

[EdDanzer]

If you use the Excel BOM feature SolidWorks is not planning to support it. I’ve has an SPR in for over 2 years. When I refused to continue maintenance until they provided a response they said replied it was not being supported. Hawkridge Systems advertises the Excel BOM as a top feature.

Needless to say I have dumped Hawkridge Systems and have started to look for a replacement CAD package.

Ed Danzer

http://www.danzcoinc.com

http://www.dehyds.com

 

[CorBlimeyLimey]

I haven't used the Excel BOM since the SW BOM was introduced. I look forward to the day when/if SW introduces it's own DT also.

"Needless to say I have dumped Hawkridge Systems and have started to look for a replacement CAD package."
Why?

 

[TheTick]

I like the Excel DT. It has all the math functions in Excel, and all the cut-copy-paste ability.

I am not looking forward to seeing a bland SW knockoff that is almost 25% as capable.

 

[handleman]

Math functions AND string functions! I like the ability to use the design table to build part numbers - as the attached file. I use the same DT template for all parts from this catalog. It makes it easy to model up the part once, change the dimension name to the corresponding dim name from the catalog, and then automatically generate the correct part number when I need to tweak it.

-handleman, CSWP (The new, easy test)

 

[CorBlimeyLimey]

Having the usual spreadsheet functions in a DT is a must. I didn't think it was necessary to point out the obvious.

Hopefully, when/if SW ever introduces its own version, it will have all the necessary functions built in. The vast majority of users do not need all the bloat of Excel. Also, IMO, the less dependence SW has on Microsoft products, the better it will be. I would like to see SW offer users a choice of using various spreadsheets.

Anyway, SW would never release a half-baked function ... would they?

 

[TheTick]

What exactly do you mean, independence from Microsoft products?

You can run SW without Excel. The Excel functionality is licensed and installed w/ SW whether Excel is already present or not.

 

[CorBlimeyLimey]

Are you sure about that? I've never actually tried to run SW without having MS Office already installed.

According to

http://www.solidworks.com/sw/support/SystemRequirements.html

Excel is required.

Computer and Software Requirements:

RAM

* Minimum: 512MB RAM (SolidWorks 2009 1GB RAM)
Parts (< 200 features) and assemblies (< 1000 components)
* Recommended: 1GB or more (SolidWorks 2009 and higher 2GB or higher RAM)
Parts (more than 200 features) and assemblies (more than 1000 components)
* Very large models: X64 processor with 6GB or more, parts with more than 1000 features, assemblies with more than 10000 components or models that exceed the limit of 32 bit architecture.
* Virtual memory recommended to 2X the amount of RAM.


Video

* A certified OpenGL workstation graphics card and driver.
For a listing of tested and certified graphics cards and driver combinations visit the Graphics Cards and Systems web site.



CPU

* Intel® and AMD® processors.
Note: SolidWorks is not supported on Apple Mac® based machines.
* eDrawings® is supported on Apple Macntosh®-based machines.


Other

* Mouse or other pointing device
* DVD drive
* Microsoft Excel 2002, 2003, or 2007
* Internet Explorer version 6.x or 7.x
* Adobe Acrobat version 7.0.7 or higher


Network

* SolidWorks is tested only with Microsoft's Windows Networking and Active Directory network environments.
* Novell networks and non-Windows based network storage devices are not tested or recommended.

 

[dgowans]

CBL,

I've installed and used SWX on my personal laptop that doesn't have any components of MS Office installed. I've not done anything with design tables or Excel BOMs on this machine, but SWX functions OK.

 

[macduff]

Guys,
My Take on this is Excel and SW tables have never been very stable in the SW software, especially on the drawing side of the software. I constantly fight with excel (very little) and SW tables moving around, fonts changing when you edit the tables, and column's not freezing when making a width change, etc...However, excel works the best in Design Tables and would hate to see that change. I love the capability of saving an Excel BOM because I can import it into our ERP system.

Just may take on this.......

Have a good day,


Colin Fitzpatrick (aka Macduff)
Mechanical Designer
Solidworks 2008 SP 4.0
Dell 490 XP Pro SP 2
Xeon CPU 3.00 GHz 3.00 GB of RAM
nVida Quadro FX 3450 512 MB
3D Connexion-SpaceExplorer

 

[handleman]

You know you can save a SWX BOM as a comma-delimited file that can be opened in Excel, right?

As far as Excel being included with SWX, you can check this quite easily. Go to your Office install directory and change the filename for EXCEL.EXE. Then try to edit a DT.



-handleman, CSWP (The new, easy test)

 

[CorBlimeyLimey]

The basic SW program, yes of course, but not the DT or Excel BOM, which is what this thread is (was ?) about.

 

[TheTick]

I just tried what you suggested, and DT's still worked. MS Office somehow created a new Excel.exe file when editing the DT in its own window.

It may not be quite that simple, handleman. API access to Excel functionality may not require the actual presence of Excel.exe, only key DLL's.

I recently read a blurb (on SW web site) that seemed to indicate that Excel license was part of SW license. I imagine it's a limited use license, similar to the way VBA objects' licenses can be limited.

 

[handleman]

The reason Office created a new Excel.exe file is that SolidWorks asked for Excel. Office automatically repairs itself when it gets corrupted. If Excel were not needed, why would Office fix itself? Also, you can check your running processes while editing a DT (in its own window or not), and Excel will be listed. If you already have Excel open and you are editing a cell when you try to open a DT, it will interfere.

I'd trust the system requirements over a "blurb", SW website or not.

-handleman, CSWP (The new, easy test)

 

[TheTick]

Not betting the rent on a blurb, either.

 

[JMarv]

Handleman,

I know this is straying a bit off-topic, but that is a very nicely done design table. Misumi's use of 3D PartStream.net makes it easy enough to configure part numbers and get models, but you've taken that one step further by bypassing the website all-together. I've often wanted to do this for some of the "configurable" components that I purchase. I've just never taken the time time to do it. On a DT like this, is it possible to "validate" (not sure if that's the correct term) some of the cells, so you can only enter certain numbers?

Joe
SW Office 2008 SP3.1
P4 3.0Ghz 3GB
ATI FireGL X1

 

[handleman]

Sure, although that's sort of an Excel question rather than a SW one. If you need to have "helper" cells (some sort of formulas, lookup tables, etc), all you have to do is put them either below the last row or past the last column of the table. SW stops evaluating the table as soon as it sees a blank row or column.

As far as Misumi components go, you'd be hard-pressed to find a model of SNLBR on the website. It comes from a Japanese-only catalog of extra-super-configurable components.

http://misumi.jp/cp/gizyutsu/fa_catalog.html.

I'm not sure if we have a special relationship with Misumi to be able to order from this catalog or if anyone can as long as they can figure out the part numbers.

-handleman, CSWP (The new, easy test)

 

[drawoh]

TheTick,

What exactly do you mean, independence from Microsoft products?

TheTick,

If SW were independent of Microsoft Applications like Excel, it could be exported to non-Microsoft OSs like Linux. I would like that.

On the other hand, I use design tables systematically, and I seriously abuse Excel doing it. I use text functions and logic, and I name cells. I do not want to multiply $A3 by pi, I want to multiply DIAMETER.

OpenOffice under Linux is very reliable at reading and writing Excel files, although not quite as user friendly. It is Free Software, so SW would be able to access the source code, and hack it or modify it.

We still use the Excel parts lists. This is primarily because we export the data to an external spreadsheet. We generate complicated assemblies, some with over a hundred parts. Such an on-drawing parts list takes over the drawing sheet, and is often better left off it. An external parts list is a useful stand-alone document, anyway. Exporting from the SW BOM is less convenient.

JHG