TheSwamp
CAD Forums => CAD General => Topic started by: 42 on May 19, 2009, 08:47:48 AM
-
Ok here is the problem.
Person A is working on the ground floor plan, person B is working on the sections. The sections have the ground floor plan xrefed in.
When person A wants to save their work in the ground floor plan a notice pops up "unable to save drawing as it is been accessed by another session"
When the ground floor plan is detached person A is able to save their work no problem.
The drawings are been held on a local network. I seem to remember this cropping up some years ago, the consensus being that iy was to do with a slow network, I'm assuerd that we have atip top network so this does not seem to be the problem................any thoughts
-
Look into "DEMANDLOAD". It needs to be turned off.
-
Ok I'll try that and keep you posted.
Thanks (if it works!)
-
Look into "DEMANDLOAD". It needs to be turned off.
I think you mean XLOADCTL. I can see where you probably got mixed up with the demand loading.
Change XLOADCTL to 2.
Turns xref demand-loading on and off, and controls whether it opens the referenced drawing or a copy.
0 Turns off demand-loading; the entire drawing is loaded.
1 Turns on demand-loading. Referenced drawings are kept open and locked.
2 Turns on demand-loading. Copies of referenced drawings are opened and locked; referenced drawings are not locked
When XLOADCTL is set to 2, a copy of each referenced drawing file is stored in the folder specified by the XLOADPATH system variable or the temporary files folder (set in the Options dialog box). Additionally, xrefs load faster when you work across a network: the performance enhancement is most pronounced when you open drawings with many xrefs.
-
Thanks for the correction Matt.
-
One might also want to set the INDEXCTL [set it to 3] variable as well.
-
xloadctl is set to 2
indexctl is set to 0
We will try the indexctl 2 setting
The same problem with xrefs is cropping up with NO other drawings related to that project open. The person in question is THE ONLY person working on that project.
Again will keep you posted.......unless I get board or forget!!
-
please use
INDEXCTL=3
-
The ability to read is so over rated :-D
-
please use
INDEXCTL=3
Michael,
What advantages do you see setting this variable to 3?
-
Because Help says so? :-)
Controls whether layer and spatial indexes are created and saved in drawing files.
To receive the maximum benefit of demand loading, it is recommended that you save any drawings that are used as xrefs with layer and spatial indexes.
0 No indexes are created
1 Layer index is created
2 Spatial index is created
3 Layer and spatial indexes are created
......
-
Because Help says so? :-)
Controls whether layer and spatial indexes are created and saved in drawing files.
To receive the maximum benefit of demand loading, it is recommended that you save any drawings that are used as xrefs with layer and spatial indexes.
0 No indexes are created
1 Layer index is created
2 Spatial index is created
3 Layer and spatial indexes are created
......
I read that too :-P Just wondered if he had any extra insight. :-)
-
yes, as long as one is indexing the data, one might as well index both the layer and the spatial data while one is at it....in most cases, unless one is using clipping depth on views, this setting should not present any issues to the user...however to prevent any issues from arising it is optimal to always set INDEXCTL to 3 as a prophylactic measure.
-
Actually, I have seen significant delays with INDEXCTL set to 3 when using XREFs, particularly during XREF loading and saving as the drawing is re-indexed.
-
From my perspective I'd rather 'see' delays than not SEE data that should be there when XREF'ed; but that is just me.
-
From my perspective I'd rather 'see' delays than not SEE data that should be there when XREF'ed; but that is just me.
Everything loads just fine with no indexing. Turning it off doesn't cause things to 'not appear'; when set it causes them to load faster (in theory), particularly under partial loading conditions.