SP3.3

Discussion in 'SolidWorks' started by andrewj, Feb 17, 2006.

  1. andrewj

    andrewj Guest

    Whats happened to the Bill of Materials Options (Part number displayed
    when used in a bill of materials - Document name, Configuration name &
    User specified name).

    I do not see it anymore after upgrading from SP2 to SP3.3

    Andrew
     
    andrewj, Feb 17, 2006
    #1
  2. andrewj

    CS Guest

    I am seeing this too
     
    CS, Feb 17, 2006
    #2
  3. andrewj

    Jason Guest

    Is the option just gone?
     
    Jason, Feb 17, 2006
    #3
  4. I was just told this will be fixed in SP4.0. Sorry folks, at this point I
    suggest avoiding 3.3, unless you require the PDF fixes, and don't care about
    part numbers in the BOM..

    WT


    *** Free account sponsored by SecureIX.com ***
    *** Encrypt your Internet usage with a free VPN account from http://www.SecureIX.com ***
     
    Wayne Tiffany, Feb 17, 2006
    #4
  5. It's really difficult to understand how they release software with so many
    obvious bugs. I mean come on. 3.3 is out for one day and already serious
    problems were found, some within MINUTES.

    This is really a weak spot in an otherwise good company.

    Best Regards,
    Devon T. Sowell
    www.3-ddesignsolutions.com
     
    Devon T. Sowell, Feb 17, 2006
    #5
  6. andrewj

    CS Guest

    It can still be set through the API. I just tested. I had created a
    custom property manager that emulated that section of the Configuration
    Property Manager Page and mine still works.

    Corey
     
    CS, Feb 17, 2006
    #6
  7. andrewj

    j Guest

    Those that feel they don't have to release SP's without going thru the
    EV testing again. The last 2 point SPs did not go thru EV testing and
    both of these have been crap releases. And it probably wont stop there.
    They fix one thing and F&CK up 20 others.
     
    j, Feb 18, 2006
    #7
  8. andrewj

    Bill Guest

    I still see the Bill of Materials Options on new configurations but
    it's gone for existing configs.
     
    Bill, Feb 19, 2006
    #8
  9. andrewj

    andrewj Guest

    We only updated to sp3.3 from sp2 because the pdf problems were fixed.
    This is absolute crap. I am sick and tired of wasting my time testing
    their software and finding stuff that is broken. We pay good money each
    year for so called maintenance. Who is going to pay me for the time now
    wasted because we have to now roll back to a previous service pack and
    then when sp4 is available, install that.
    SolidWorks this is just not good enough and maybe some acknowledgement
    that there are problems is required.

    rant over....
     
    andrewj, Feb 19, 2006
    #9
  10. andrewj

    j Guest

    This is not the only thing missing in SP3.3. There is now no option TO
    EXCLUDE FROM BOM in an assembly when you RMB on a part or subassembly to
    change the configurations of that part/subassembly.
     
    j, Feb 21, 2006
    #10
  11. andrewj

    Jason Guest

    Well that option is part of the same area of the config dialogue that's
    missing. So it's the same problem not really two.
     
    Jason, Feb 21, 2006
    #11
  12. andrewj

    j Guest

    Seth is correct. This is in the assembly. The funny thing about this is
    if I pick more than one part at a time this option is available. Single
    parts are not allowed to be excluded.
     
    j, Feb 21, 2006
    #12
  13. andrewj

    CS Guest

    I have to say that from a programming standpoint it is very easy to
    cause a Property Manager Page to be missing sections. If one item
    causes an exception the PMP will load up until that point and skip the
    rest but give no errors. Don't flame me for this but there is alot of
    behind the scenes changes going on in solidworks in 2006 (I believe the
    modeling kernel underwent alot of changes to speed up large assemblies
    among other things) they are in the beta process of implementing 64
    bit, the change from BlueBeam to Acrobat among other things. These are
    huge implementations that touch every part of the rest of the software.
     
    CS, Feb 21, 2006
    #13
  14. andrewj

    j Guest

    This and the other config problem are reported to be fixed for SP3.4
     
    j, Feb 21, 2006
    #14
  15. andrewj

    Jason Guest

    I'm thinking that sp3.2 which is the 64bit version pre-release might
    have integrated code that contributed to this. So there was probably a
    lot more behind the scens code changes than ususally for a SP. I'm
    speculating of course.
     
    Jason, Feb 22, 2006
    #15
  16. andrewj

    Jason Guest

    I think it is a compiler option but some things may need optimizing to
    run on 64bit which may mean code changes or rewrites. And rewriting
    code to take more advantage of 64bit abilities will be advantageous to
    all eventually.
     
    Jason, Feb 22, 2006
    #16
Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.