Who reckons it's a bag of nails? It sort of works some of thetime but push it with bigger assemblies and reference files over anetwork then don't expect to see the model all back togetherwithout mate problems or can't find files when you come back to itat a later date.
By adding the year to the name it forms a trap whereby new softwarehas to be released otherwise it looks dated. Forget the date andget the annoying bugs out the thing.SolidworksGeneral
By adding the year to the name it forms a trap whereby new softwarehas to be released otherwise it looks dated. Forget the date andget the annoying bugs out the thing.SolidworksGeneral

my software works fine.
It sounds like you have file and organization issues more so thanSolidworks problems. Although you may have a point, maybeSolidworks should look into 'dumming' down the behind the scenesfile managment that we all do behind the scenes. And please, ohplease don't mention pdm!
But good luck finding you files.
Don
If your having problems with your software (eg. bugs, lockups, etc)why not state your problem(s) then we can try to help you.. Justcoming here and complaining doesn't do anyone any good.. Unless youjust needed to vent.. We all need that at times..
Working over the network with a large assembly is not bestpractice.. Thats alot of information to run over a pipe.. Bestpractice is to work locally. For small parts, and small assembliesI have no problems with my network, but once I see slowdowns I packand go to my HDD and that usually solves my problems..
But if you rip out the circuit board of the ATM, it won't functionproperly either...
1. state your problem
2. Tell us your computer specs (see my sig)
3. Tell us what version and sp your running (see my sig)
Or call your VAR if you have an active subscription.. That's whatyour paying for..
John Nickson wrote:
Gave up on pack and go months ago, that didn't work properyeither.
John Nickson wrote:
mmm.. should I trust my calculator any more? Hey, it's a goodjob they found some humans who managed to get ATM softwareright.
We manage to build very large assemblies (thousands of parts) andrun it over a network without PDM. It can be done... but, it'sdefinitely not my first choice. What level of SW do you have? Ifyou have PDMWorks for Workgroups you should try it. If you havereally large assemblies like us, try setting up a vault perproject.
Don,
I agree that it sounds like poor file management discipline. Icannot emphasize 'discipline' enough... and everyone in the gamehas to play by the rules. Regarding PDM... it doesn't get anySIMPLER than PDMWorks for Workgroups. If you can use WindowsExplorer, you can use Workgroups!
I can't leave w/out an ATM comment... too bad their voting machinesweren't as good as their ATMs!! Maybe we could all vote at theATM?!?
Yes, I can say that... I'm from Ohio and drive by their HQ almostdaily
Have a good day, everyone!
I suppose with enough experience one can start to know what worksand what doesn't, which methods do and which don't - and when. Butit's everything from straight-forward for large assemblies. That'sjust my view on it
We are running SW2009 SP3.0
Pentium dual processor 3.40Ghz
4 GB memory.
I can use Microsoft Word, Excel and Access all day and they don'tloose data, take forever to process data or crash.
Maybe we're pushing SW beyond it's capabilities?
In all seriousness, you are at the upper limits of the softwaredepending on your files complexities. I really wish there was abetter way without pdm for solidworks file manipulation. Pack andGo is a good start but..... it has a long way to go.
I put in an ehancement request for a new assembly format a year or2 before pack & go was released. I wanted an assembly fileextension of .sldzip or something. And the way I invisioned itworking is you would convert a regular assembly or drawing for thatmatter, into this .sldzip file. The system would then go and grabALL of the components and files and embed them into ONE file withthe .sldzip extension. The system would still retain remember wherethe orginal folders were for later decompression of the file, butyou would only need the 1 file to work with that assembly ordrawing. Great for taking things home.... 1 file. Take that onefile home, work on it just as one file, and them bringing back towork to decompress back into the original file system or pdm ifneed be.
The point is that you could work from one file and one file only,regardless of assembly or drawing. And then about a year later theycame out with pack & go..... It's great start, but not what Iinvisioned..... I don't want to have to keep track of structurewhen I leave with an assembly or drawing.
I should note, I realize that on very large assemblies this wouldrequire a lot of resources, but lets face it, with 64 bit memoryaddressing and today's cpu's (SSD's as well), I think were rightthere to impliment such functionality.
Don
John Nickson wrote:
We are running SW2009 SP3.0
Pentium dual processor 3.40Ghz
4 GB memory.
I can use Microsoft Word, Excel and Access all day and they don'tloose data, take forever to process data or crash.
Maybe we're pushing SW beyond it's capabilities?
When was the last time the OS was freshly installed..
What OS are you using? if you bump up to a 64bit OS, you can addmore ram..
You say a Pentium Dual Proccessor? what exactly does that mean? APentium Dual Core, Core 2 duo, etc?
If your running a ~15,000 part assembly over the network, then yea,I would think you would have problems.. thats alot of data totransmit over a WAN..
and your comparing apples to elephants there John.. trying tocompare a word processor, spreadsheet and database program to a 3DCAD program.. I don't see how either of those 3 can be evenremotely close to SolidWorks..
John Nickson wrote:
Maybe the machine was fine but a human put twenties in the tensslot??
hope you get your problem sorted.