Académique Documents
Professionnel Documents
Culture Documents
32Replies LatestreplyonJun4,20145:35PMbyRickSink
JakobArent May6,201312:34PM
Howcanistopshowing"adocument
named"xxxx"isalreadyopened"
whenopeninganAssembly
ThisquestionisNotAnswered.
Hello,
Needsomehelpwithanissuewhenopeninganassemblyinsolidworks.After
changingthenumberingsystemihavesometroubletoopenanassembly.The
message"documentnamed"xxxx"isalreadyopened,doyouwanttoshowthis
alreadyopeneddocument?"appearstoooften....Idon'thaveaproblemtoclick
onyes.....butbecausemyassemblyhasmanyofthesamepartthemessage
popsupmanymanymanytime.Toopentheassemblyineedtogothrough
many(100)click.Andthatisfrustrating....Thethingisnoteveymultiplepart
isdoingthatjusttwoorthree"specialparts"seemtohavethat.Triedtoclean
thesessionandrenamepart.Evendeletedoneofthepartsandcreatedanew
part...Butitisstilldoingthat.Issomebodyabletohelpme?
Thanks
Ihavethesamequestion(0)
5844Views
Categories:Assembly,SolidWorks
Tags:
HelloJakob,
Itsoundslikeyourassemblymaybereferencingmorethanonepartwiththe
samename.Youmighttrymakinganewfolder,thenwhenyougetyour
assemblyopen,doaPackandGooperation(File>PackandGo)intothisnew
folder.Thatwillcopyyourassemblytothenewfolder,alongwithalltheparts
andassembliesthatitcontains.IfthatworksOK,thenusethisnewassembly
insteadoftheoldone.
Actions
Like(0)
Thishasrecentlystartedtohappenalotforusaswell.Isearchedourentire
networkandthereisonlyonecopyofthepartsthatitasksabout.Italso
happenedwhenIfirstopenedmymodel,andIclicked"no"toeverypart,then
closedandreopened,andeverythingworkedfine.Soitdoesn'tseemtobea
problemwiththeactualparts,anditsadifferentparteachtime.
Italsoseemstobearecentproblem(maybeMayorevenJune),butmy
coworkersarestillonSP2,anditstartedhappeningtothemaroundthesame
time,eventhoughtheircomputershaven'tbeenupdated.Coulditbepossible
thatmyopeningapartwithSP3isnotcompatiblewiththeirSP2andvice
versa.Wewilltrytoupdatetheircomputersandseeifthathelps.
Actions
Like(0)
Iaminthesameboatasyouare.Ionlyhaveonepartfilethatisusedin
severaldifferentassemblymodels.Theseassembliesarethenusedto
createafinalassemblyofthepieceofequipmentbeingmade.Itbecomes
extremelyannoyingwhenthereisnothingdifferentaboutthepartfiles,
theirlocationsoranythingelse.Itishappeningonallofourcomputers
here.Originallywethoughtthatsomeonehadthesamepartfileopen
elsewhere,butthatisnotthecase.Itwouldbegreatifsomeonefrom
Solidworkscouldatleastcomeupwithanexplanationforwhythisis
happening.
Actions
Like(0)
Ihaven'tseenthishappen.I'monSP4.0EV.Itsoundslikea
combinationexternalreferencetypesisconfusingSolidWorks.
Forexample,ifyouhavewidgetwithincontextreferencestoa
phalangieinablammerassemblyandalsothesamephalangieina
plopperassembly,Solidworksmightgointoaperiodiccycleofloading
thewidgetandthephallangieasblammerassemblyreferencesandthen
loadtheexternalrefernecesofthewidgetwhichincludestheplopper
assemblywhichincludesanotherreferencetothephallangieandinstead
ofusingthephallangieinmemory,ittriestoreopenit.Itmightdothis
foreveryreferenceofthewidgettothephallangieoreveneveryfeature
inthewidgetwithanincontextreferenceuntiltherebuildsconverge.
Sothat'saworkinghypothesisthatmatchesthesymptoms.Itcouldbe
wrong,buttheprocessofestablishingthatit'swrongwillprobablyreveal
othercluesaboutwhat'sgoingon.
Thenextstepistofigureoutthetopologyoftheassembly.Thebest
toolIknowoffordoingthatisthesaveandcheckindocumentdialog
ofWorkgroupPDM.Thisgivesyouatreestructureofallofyour
assemblyreferencesandcalledexternalreferencesandtheirnestedtree
structures,soyou'llbeabletoidentifyrecursion.Youcanexportthatto
adelimitedtextfileforfuturereference
Lookforinstancesofpartsappearaningintheassemblytreeandthe
externalreferencestreeofanassemblycomponent.Seeifbreaking
thoseexternalreferenceshelps.
Actions
Like(0)
Anotherpossibilityoccuredtome.
IfyourecoveravirtualcomponentfromtheSolidWorksbackup
directoryandloadtheassemblycontainingthevirtualcomponent,often
itwillnotstorethecomponentintheassemblydespiteithavingthe
nomenclature<#assemblyname>^<#component_name>.sldprt,itwill
bestoredoutsidetheassemblyandcheckintothevaultwiththatname
anddoallkindsofcrapthatvirtualpartsshouldn'tdo.Ifthathappens
andyoumakeanewvirtualpartwiththesamename:like
<#assembly>^<part1>,thenIcouldseeSolidWorksalternating
betweentherecoveredpartandthevirtualpartwhichisunpackedtoa
temporaryfolderwhentheassemblyisopened.WithSolidWorksgoing
backandforthonthat,itmightthrowdialogsliketheoneyoutalked
about.
Ifthat'sthecase,youneedtorenametherecoveredvirtualpart.
Actions
Like(0)
Yourfirstscenariomakessomesense,howeverallthepartsare
individualpartswithnoincontextreferences.Icanopenone
assemblythatcontainsfourpartsthatarealsoinasecondassembly.
IfIweretothenopenthesecondassembly,thismessageappearsfor
eachofthefourpartsthatarealsointhefirstassembly.Wehaven't
changedanythingwithhowthepartsorassembliesarecreated.All
thepartsthatSolidworkssaysarealreadyopened,technicallyare
opened,butshouldn'taffecttheopeningoftheassembly.
Actions
Like(0)
Tobeblunt,youhavetwofilesnamedthesamethingintwodifferent
locations.
Iftheyaresupposedtobediffernent,thennamethemdifferentnames.
Iftheyaresupposedtobethesameyouneedtoinvestigate.SWistellingyou
theyaredifferentfiles.Lookatthereferences.Youwillfindthatoneislocated
onyourdesktopandtheotherissomewhereelse.Theycouldbetheexact
samepartfromthegeometrytothefilepropertiestothedocumentproperties
butsinceyoucopiedthefile(probablypackngo)thentherearenowtwo
seperatereferencesforthesamepart.
Ifthisisnotit,thenuploadyourfileshere.StartwithanewsessionofSWand
recreatetheproblem.Onceyoufoundtherighttwoassembliestocreatethis
problempackngothosetwoassemblies.Iftheyaretoobigthenzipthemand
providethedropboxorgoogledrivelocation.
Actions
Like(0)
Hi,Isearchedmyentirenetwork,andthereisonly1filewiththenamethat
comesup.Iknowthatmultiplefileswiththesamenameisbad,andsince
I'vebeenhere,havebeencleaningupsomeoftheolderstuffthatwasdone
thatway,buttheseparticularpartshaveonly1copy.
Sorryforreplyingsolate,I'vebeenoutoftheofficefor3weeks.
Actions
Like(0)
Trythistoseeifitworksforyou.GotoSystemOptionsExternalReferences
Loadreferenceddocumentsandselect"None".Ihadthesameproblemand
thisworkedforme.Goodluck.
Actions
Like(0)
Iagreewiththeoriginalpost.Yes:theremaybearefenceissue.No:Idon't
carewhenI'minahurry.A'yestoall'(thissessiononly)checkboxwouldbe
mosthelpful
Actions
Like(0)
Wearehavingproblemswiththis,too.IfIchangeconfigurationsofan
assemblyitseemstothinktheblastedpartsfilesusedintheoriginal
configurationarestoredsomewheredifferentfromthoseinthenew
configuration,andI'mspendingages,clickingthesillybuttonlikeI'mshooting
spaceinvaders.WEHAVENOTMOVEDOURFILESANDTHERE'SONLYONE
COPYOFTHEMONTHESERVER.
Anthony'srequestfora"yestoall"buttonwouldbeabrilliantideaifthe
originalproblemofwhySWthinkstherearedifferentpartscannotbesolved.
Actions
Like(0)
Thisseemstobeanissuethatwasstartedinoneoftheservicepacksin
2012.We'verunintothisaswell&allofthefilesthatitistryingtoopen
arewithinthesamefolder.Wegetthisalotwithstandardhardwarethat
we'veplacedintotheassemblyfilefromthestandardsfolderwehave&
thensavethemintothejobfolder.AlmostseemslikeSolidworksisplacinga
mapinthefoldertopullfilesfromtheoriginalplacetheywerepulledfrom
firstratherthanthefolderthatitiscurrentlysavedin.Idoseein2014they
addedatickboxinthatdialogtonotaskagain.
Actions
Like(0)
Wehaveranintothisissueafewtimesoverthepastcoupleweeks.atfirsti
honestlythoughtitwasauserissue,becauseineverhadtheproblemwheni
openeduptheassembliesonmycomputer.
butitturnedoutthatitwasntauserissue.itwasaissuewithourfilelocations
andnames.Wehadafewpartsthatwouldcreatethispopup.mysuggestion
wouldbetoinvestigatethefilelocationsmanuallyviarightclickingandviewing
thepartproperties.forsomereasonwhenicheckedthereferenceswiththe
file/findreferencescommand,thepartsshowedupinthesamelocation.but
whencheckedmanuallyviarightclickingonthepartandviewingthe
properties,thelocationsweredifferent.onceiupdatedthefilelocations
manually,myproblemwasfixed.hopethishelpallofyou.
2013sp5
Actions
Like(0)
Wehavehadthissameissue.WerunSW2013,SP4.0.We"fixed"itby
changingthethresholdforLargeAssemblies...Tools/Options/Assemblies/check
LargeAssembliesandthenenteranumbersmallerthantheassemblythat's
givingyouaproblem.Thiswillforcetheassemblytoloadlightweight.
ThisisnotarealfixinthatIthinktheonlyreasonitworksisthatpartsarenot
beingtotallyloadedandtheirpaths,iftheyaredifferent,arenotbeing
detectedbySW.
Diggingalittledeeperintothis,intheassembly,youcanRTCLKonapartthat
isgivingyoutrouble,thenselecttheComponentPropertiesiconforthepart.
Thedialogboxthatpopsupwillshowthepathtothepart.Whenwedidthis,
wefoundthesameparthaddifferentpaths.Butitwasevenmoresubtlethan
this.Belowaretwopathsforthesamepartthatappeartoactuallypointtothe
samelocations...
\\mainserver\share\R&D\CAD\WIPREADERSFLATFOLDER\HDW0018.SLDPRT
S:\R&D\CAD\WIPREADERSFLATFOLDER\HDW0018.SLDPRT
Boththesepathsareonournetwork,andthepartonlylivesinoneplace,but
SWthinksthereisaslightlydifferentpathdesignation,dependingonwhich
occurrenceofthepartoneislookingatintheassembly.Idon'tknowwhether
thisisaSWproblemoraproblemwithournetworkconfigurationorsetup.I'll
havetoleavethistootherstofigureout.
Hopethishelps.
Rick
Actions
Like(1)
ThisistheconclusionthatIhavecometoaswell.Ihavebegannoticing
thatthefilepaththatSolidworkswillusetoopenapartwillvarybetween
thenetworklocation,andthelocallocation,eventhoughthefileislocal.
It'shardtounderstandwhySolidworkswouldgothroughthenetwork
locationtoopenalocalpart.Iamhopingthereisasimplesolutiontothis.
Actions
Like(0)
Rick,
I'vebeenlooselytrackingthisthreadfornearlyayear,andwasplesedto
seeyourpostlastnovemberthatclearlydefinedtheproblemaswehave
beenexperiencingitforroughlyayear.Forus,theproblemiscearlya
"mapeddirvevsnetworkpath"(A.K.A.LFSvsUNCpath)issue.Theearly
poststhatblamedtheproblemonactuallyhavingtwoseparatecopiesofa
filewereclearlynotunderstandingtheproblem.
I'mgladtoseethatourcompanyisnottheonlyonewhoisexperiencing
thisproblem,andfeelingstronglythatit'ssomethingSWshouldhavebeen
abletofixbynow.IagreewithJimthatthisproblemseemstohave
surfacedinanearlySPfor2012.Wejustupgradedto2014SP3yesterday,
andIalsoagreewiththecommentsthat"donotshowthisagain",while
helpful,isnotasolutiontotheprolem,becauseIdowanttobenotifiedin
therarecasethatsomeone"breaksprotocol"andcreatesa"legitimate"
duplicatecopyofafile.
OurVAR(whohastypicallybeenverygoodatresolvingproblemsforus)is
currentlyinvestigatingthisproblematmyrequest.Clearlythisisanelusive
one.Ihavecomeupwithasimpleandrepeatableprocessforcreatingthe
probleminournetworkenvironment,butstilldon'thaveanyinsightinto
whySWseestheLFSandUNCpathsasdifferentfiles.Also,Ihavenot
beenabletoreproducetheproblemonmyhomenetwork,norhavemy
colleaguesattwoothercompanylocations.VERYFRUSTRATING!
Bytheway,I'vebeenaSWuserforabout7years,andpreviouslyUG,
Pro/E,&Inventorbutthiswholeblogthingisnewtome,sopleasebekind
ifI'vebrokenanyblogetiquette.
Tim
Actions
Like(0)
Tim,
AftertalkingtoourITguruandgettingremindedoftheproblemin
moredetail,hereiswhatwedo.Themosteffectivefixistonotallowa
UNCpathreference(\\server\share\file_path\part.sldprt)toanySWfile
andasimultaneousdriveletterreference(S:\share\file_path\part.sldprt)
tothesamefile.SWwillthinkthesearedifferentpartswithsamename
eventhoughit'sliterallyonepartresidingononedrive...andSWwill
throwupthe"alreadyopened"error.Ourpolicyhereisthatwealways
surftothedriveletterreferencewheneverinsertingexistingfiles(like
screws,etc.)intoanassembly.WeavoidtheUNCreferenceslikethe
plague.
SeemslikeSWcouldeasilyfixthis,butI'manME,notasoftware
engineer.
Hopethishelps.
Rick
Actions
Like(0)
Rick,
Thanksforthefeedback.I'mstillinthemiddleofatroubleshooting
effortwithourVAR,butthatwasexactlyhisadvice:pickoneorthe
other(UNCorLFS)andjustavoidtheother.Wealsowouldliketo
avoideverusingaUNC.Ourbiggestproblemwiththis(andthe
sourceofmostofourUNCreferences)isWindowssearch.Thisishow
wefindspecificpartnumbersmostofthetime(noPDMsystem).
Andforsomereason,WindowssearchalwayscomesupwithUNC
pathsintheresults.Soanytimeweopenandassembleapartfrom
thesearchresults,wecreatetheanotherinstanceofproblem.
Avoidingthisrequiresextratimetonavigatetothefolderusingthe
driveletter.Idoitalot,butwishIdidn'thaveto.Doyouuse
Windowssearch?DoesitgiveyouUNCpaths?Anybodyknowifthis
behaviorcanbechanged?
OursecondproblemisthatwehaveSOMANYinstancesofthe
problemalready,andcleaningthemupistimeconsuming.Themost
reliableapproachIhavefoundisasfollows:
1. CreateacopyofthecomponentwithUNCpathreference
2. Opentheparentassy
3. ReplaceoriginalcomponentwithcopyTAKINGCARETO
NAVIGATEVIADRIVELETTER
4. Savetheassembly(notsurewhetherthisstepisrequired)
5. Ensurethattheoriginalcomponentisnotinsession
6. Replacethecopywiththeoriginal(AGAIN,DRIVELETTER)
7. Savetheassembly
8. Deletethecomponentcopy
REPEATFOREVERYCOMPONENTOFEVERYASSYTHATINCLUDES
AUNCPATH.WOW,THEREMUSTBEABETTERWAY!
Aswithmayotherswhohaveposted,Ijustcan'tunderstandwhy
thiswouldhaveshownupina'recent'release,unlessitissomething
thatSWisdoingdifferently,andoughttobeabletofix.
I'llkeepafterabettersolutionthroughmyVAR,untilIhitabrick
wall.IthinkIseeoneupahead.Wishmeluck.
Tim
Actions
Like(0)
Tim,
WeusetheInsertComponentsdialogboxinSWtoinsertan
existingpartintoanassembly.IchoosetheBrowsebuttoninthis
boxandthenjustsurftoaDRIVELETTER/folderforthepartand
lookforthecorrectfileicon...theUNCpathneverpopsup.BUT,I
seewhatyoumean...ifyoudon'tselectthefiledirectlyfromthe
listandifyouusethesearchboxinsteadonthisscreen,the
resultsturnupinUNCformat!Andifyouselectthepartthisway,
yougetaUNCreferencedpartandyouareprobablythenhosed.
Beforeweknewabouttheproblem,Ithinksomeofusweredoing
thisandselectingparts.I'vejustgottenintothehabitof
searchingforfilesdirectlyontheiconsandnotusingthesearch
box.This,ofcourse,meanseverybody'sPCmusthavedriveletter
mappeddrivesandSWfolksmustuseonlythesetoinsertparts.
And,ofcourse,youlosethepowerofthesearchbox.
Andyes,it'saroyalpaintofixalltheUNCpathedparts!
I'vebeenusingSWforyearsandIdon'trecallthisproblem
beforeeitherrev12orrev13,butI'mnotcertain.
PerhapsoneproblemthatSWcannotaddressisthatifthe
programencountersaUNCpath,itdoesnotreallyknowhowyour
drivelettersaremapped...evenifoneismappedtothesameUNC
location.SomehowitwouldhavetodiscovertheUNC/LFS
relationship.Again,abovemypaygrade)
Rick
Actions
Like(0)
Rick,
(alsoJacob,Justin,Dean,Nigel,Jim,Nicholas,Mark,Bruce,
John,andanyoneelsewhohasbeensufferingfromthis
problem)
ItappearsthatourVARhasfoundasolutionthatworksfor
us,andI'mcuriouswhetheritworksforanyoneelse.Itisso
simpleithurts,afterallthecountlesshoursI'vespentdealing
withandtroubleshootingthisproblem:
1. Addyour"primary"folder(s)whereyoustorefilestothe
SystemOptions/FileLocations/ReferencedDocuments
folderlist(ourswasempty),usingtheyourpreferredpath
(mappeddriveletter,inourcase,NOTUNCpath).
2. Also,underSystemOptions/ExternalReferences,check
the"Searchfilelocationsforexternalreferences"option
(ourswasnotchecked).
THAT'SIT!Iamnotabletoproducethemessagenow,
exceptinlegitimatecaseswherearealduplicatefileexists(I
createdonefortesting).
Now,thereweresomeotherstepsthatIwentthroughduring
thetroublshootingprocess,includingalittleregistryeditingto
cleanupsome"offlinefile"history.Butintheend,Iam
doubtfulthathadanythingtodowiththeproblem.Ifanyone
isinterestedinmoredetail,justletmeknow.
Also,ifyoufindthatthisfixworksforyoutoo,letyourVAR
know,becauseobviouslytheyhavenotbeenabletosolvethis
problemformanyofyoueither.
Tim
Actions
Like(0)
Tim,
Well,Itriedthisanditdoesappeartowork.Itried
insertingpartsbysearching,andwhilethesearchshowsa
UNCpathonthepart,itdoesnotappearto"stick"once
thepartisinsertedintoanassembly.Soyoureallymay
havefoundafix!!
TellyourVARtoworkontheDynamicHighlightcheckbox
problemnext!!!!!
Rick
Actions
Like(0)
>>>Hi,Isearchedmyentirenetwork,andthereisonly1filewiththename
thatcomesup.Iknowthatmultiplefileswiththesamenameisbad,andsince
I'vebeenhere,havebeencleaningupsomeoftheolderstuffthatwasdone
thatway,buttheseparticularpartshaveonly1copy.
Whenwestartedgettingthesemessages,Iwentthroughandmaded@#*ed
sureIonlyhadonesourcefileforthepartsshowingup.Theseallcomefrom
onelocation.Therearenoduplicatefilenames.
NexttimeIwenttoopenthissameassembly,aDIFFERENTcomponentgave
methesamemessage.I'vebeenusingSWsincetheyear2000,havenever
workedinacompanythathadEPDM,andhaveneverhadthisproblembefore.
Theproductswemakearesnowflakes,verysimilar,butneverexactlythesame.
Theyalluseusethesecommonparts/assy's.
Thisisanew"undocumentedfeature".MyfavoritehelpdesktechatmyVAR
(whoisprettyd@#*ed sharp)cannotfindasolution,otherthan"BuyEPDM".
Notananswermybosseswillaccept.Ican'tdoapackandgoonallthesefiles,
I'dendupwith50folderswith50commonpartfiles,plusalltheduplicated
hardware.Notacceptable.
SWneedstofindthecauseofthisbugandfixit.NOW.Itneverhappened
beforethelaterSP'sfor2012,andcontinuedinto2013.Ifthisneverhapened
forover12years,whyisithappeningnow?
Jim
Actions
Like(0)
updateonourassembly.theproblemisback,butitonlyshowsupforourone
user.anyoneelsewhoopensupthisassembly,opensitjustfine,noerrorsat
all.thefilelocationsshowthesameonalltheparts.checkinghissettingsand
willseehowthisgoes.
Actions
Like(0)
Checkhisloadlightweightsettings...seemypreviouspost.Inmycase,fora
largishassembly,changingthethresholdfrom500partsto1500parts
"solved"theproblem.Ofcourse,youhavetobeloadinglightweighttobegin
withforthistowork.
Ihavestillnotcomeacrossarootcausefixforthisproblemtoeliminatethe
UNCdriveversusmappeddrivereferencestothesamepartinthesame
folder.
Rick
Actions
Like(0)
Thatmighthelpifwewereusinglightweightmode,butwe'renot.Next
contestant,please...
Actions
Like(0)
AsRicksaysitisdefinitelyamappeddriveproblem.Thesimplefixis
tosimplydeletethemappeddrivefolderandputtheshortcuttothe
networkfoldersomewhereelsesoitisnotassignedit'sowndrive
letter.
Inourcasewehadtoredothefilelocationsfortemplatesastheyare
inthenetworkfolderandthatwasit.Nowinsteadofgoingto
X:/drawingswegotoC:/drawings(server)Shortcut.Theextraclick
ofgoingintoC:thenthefolderiswellworthitforthehundredclicks
savedwhenwehadtoopenanassembly.
Actions
Like(0)
>>>AsRicksaysitisdefinitelyamappeddriveproblem.The
simplefixistosimplydeletethemappeddrivefolderandputthe
shortcuttothenetworkfoldersomewhereelsesoitisnot
assignedit'sowndriveletter.
Thanksfortheinput,butifthisisamappeddriveproblem,why
diditnevershowupbetween2000and2012?Thisisabugin
thesoftware,thateverytimeIapplyanewworkaround,findsa
differentwayofexhibitingitself.It'slongpasttimeforDassault
tomanupandA}admitthereisaprobleminthecodeandB}fix
theD@#$code.AsIsaidbefore,I'vebeenusingSWfor14years
now,andneverhadtheproblemuntilthelaterSP'sof2012.We
spendtoomuchmoneyonthisproducttobeexpectedtojump
throughhoopstocovertheirbuttssothattheydon'thavetofix
theirbadcode.Thatisnotonlyunacceptable,butdeeply
unprofessional.Irealizethatitmightcosttheshareholders
.00001centeachtofix.Tough.It'stimetotakecareofthe
customer.Doit.NOW.
Actions
Like(1)
I'veonlynoticedthiswhenweupgradedto2014forsome
reason.Iamnotsureifthisistheissueorhowtofixityet,
butIhaveanassemblywithmultipleconfigurations.The
differenceintheconfigurationsismainlyaparticular
subassembly.eachoneofthesesubassemblieshasidentical
parts,exceptformaybeafew,likelongerposts....etc.It
happensmoreoftenwhenIopenadrawingreferencingeach
oneoftheseconfigurations.Ilookedupthepropertiesonone
ofthepartsthatwerepoppingupwithanalreadyopendialog
box.Thefirstconfigurationwasfine(F:\engineering\.....).
However,whenIcheckoneoftheotherconfigurationswith
thatsamepartitwasshowing(\\Goliath\engineering\.....).
IamcuriousifSWisthinkingthoseare2seperatelocations
wheninfacttheyarethesamelocation.Mydrivehasalways
beenmappedthesameandwehaveneverallowedsolidworks
tolocatefilesdirectlythroughthenetworklikethat.Atleast
tothebestofmyknowledgeanyway.
Actions
Like(0)
Bruce,
ItwouldprobablybeagoodideatoshowthistoyourVAR.
Youmayhavediscoveredaparticularlyinsidiousbug.
JerryS.
Actions
Like(0)
Jerry,pleasereadtherestofthethread.Severalofus
havebeenworkingwithourVAR's,tonoavail.Thisisa
nastylittle"undocumentedfeature"thatisobviously
hardtotroubleshoot,sinceitappearsinoneplace,but
notanother,or,oncefixedforonepartshowsupfor
another.Ifnothingelse,readmyposts,they'llbring
youuptospeedonthis.
Iseeyou'vepostedalot,soyouprobablyhavesome
prettygoodknowledgeandarehelpful,butc'mon
friend,getthefullpicturebeforejumpingonthe
simplestsolutionPassthebuckAtleasttwoVAR's
andsupportpeopleatSWareveryawareofthis.I've
workedwithaverysharpsupporttechandspokento
SWaboutthis.
I'malwaysarottenSOBonModaymornings,anda
wise@&&ingeneral,sopleasetakemyrantwitha
grainofsalt...butdoreadthewholethread.Youmay
discovertheanswer,andameanstoperpetualmotion,
justbyspendingthefewminutesrequired...
Jim
Actions
Like(0)
Jim,
Ihadbeenreadingthethreadasitdeveloped,but
sinceithasbeenrunningforoverayear,it'sabit
hardformetokeepitallstraightwithoutgoing
backandrereading.Idon'thavetimeforthatright
nowI'mluckytofindtimetovisittheforumsat
all.IsuggestedthatBrucepushthistohisVAR
becausethemorepeoplewhoreportproblems,the
morelikelySolidWorksistofixthem.
Your"rant"didn'tupsetme.You'requiterightto
notethatIclearlyhadn'tkeptupwithitall.Ihope
myanswerdoesn'tbugyou!
JerryS.
Actions
Like(0)
Idon'tthinkit'samappeddriveproblem.Thisstarted
backinoneofthe1stcoupleofservicepacksin2012.We
don'tworkoveranetworkwithSWfiles&thishappensto
usalot.Theonlythingthey'vedonetofixitistoaddthe
Dontaskagaintickboxwhenthepromptcomesup.
Actions
2014DassaultSystemes
SolidworksCorp.
Like(0)
Followus
Home|TopofPage|Termsof
Use|PrivacyPolicy
20072015JiveSoftware | Poweredby