Topic: New Figure Prefix Library and Descriptor Key Setup

[Dent Cermak]

Some powers that be in the local Corps of Engineers office have been convinced that quality drawings CAN be created in AutoCad and that Anygraph is not the ONLY answer to their needs.
We have a large Corps contract on the horizon.
My goal is to set up my system so that the field crews do not have to change a thing in their field work. This will require me to establish a Figure Prefix Library and Descriptor Key set up using the same codes as on a normal job but have the data go to the screwy Corps layers and the same codes load the Corps blocks when I run the FBK file.
How can i do this without over writting my existing files?
I do have a Corps prototype file set up and I have a Corps.dwt file set up that works well.
How do I set up 2 different sets of files for 2 separate drawing standards and not have one erase the other?
Remember, I am on LDD7 and LDD8 in the office.

[mjfarrell]

in the project settings..

here is half a hint at how it works...
Solution


Check the default settings as follows:

In the Edit Label Styles dialog box, Point Label Styles tab:
Point Label Styles Name <active desckeys only>
Description Key Matching (selected).
DescKey File: <Default>
Ensure the DescKey File name used is the desired description key file.
In the Labels Settings dialog box, Point Labels tab:
Current Label Style <active desckeys only>.

In the Point Settings dialog box, Insert tab:
Under Point Labeling, ensure the Use Current Point Label Style When Inserting Points option is selected.
The Current Point Label Style is <active desckeys only>.
On the Description Keys tab of the Point Settings dialog box:
Verify that the Description Key Search Order and Matching Options are set as desired.
Verify that the path to the description key file is correct. By default, the description key file for a project is named default.mdb and is located in the following folder: C:\Land Projects\<project name>\cogo\DescKey. You can create additional description key files. All description key files for a project must reside in the following folder: C:\Land Projects\<project name>\cogo\DescKey.


If you want to use anything other than default one changes that under the Label Settings...don't ask me why, however that is whaere one would point to an alternate desckey set

see also: http://usa.autodesk.com/adsk/servlet/ps/item?siteID=123112&id=12051562&linkID=9240777

http://usa.autodesk.com/adsk/servlet/ps/item?siteID=123112&id=2868212&linkID=9240777

[sourdough]

Some powers that be in the local Corps of Engineers office have been convinced that quality drawings CAN be created in AutoCad and that Anygraph is not the ONLY answer to their needs.
We have a large Corps contract on the horizon.
My goal is to set up my system so that the field crews do not have to change a thing in their field work. This will require me to establish a Figure Prefix Library and Descriptor Key set up using the same codes as on a normal job but have the data go to the screwy Corps layers and the same codes load the Corps blocks when I run the FBK file.
How can i do this without over writting my existing files?
I do have a Corps prototype file set up and I have a Corps.dwt file set up that works well.
How do I set up 2 different sets of files for 2 separate drawing standards and not have one erase the other?
Remember, I am on LDD7 and LDD8 in the office.

I also found that when I had to do things for 2 different cities it was also easy to go through and save your profile for LDD with the original standards, and copy it and save to a new profile name, say Corps LDD in that profile just repoint to folders that are a pointing to folders that you want to be different. It isn't to hard to copy the locations that Mike has mentioned and save any corps to the newly pointed locations. So, if I had 2 different descriptor key files you just copy and rename and in your Corps profile add/change according. Be sure that once done you go to the profile tab and export that .arg file in case something goes amiss. I'm sure you have a good understanding where LDD hides it's files.

MJP

[mjfarrell]

It is strongly encouraged that one employ the use of Prototypes, and Project settings to achieve the desired end state.  These are easier than profiles to share with other users.  Also encourages proper use of the Project Management functions of Land and limits 'accidentally' starting a job while in the 'wrong' profile.

One can use profiles however be aware they do introduce the potential for error.

[Dent Cermak]

I understand the second descriptor key setup, my main problem lies in the figure prefix library. I can deal with modifying existing files and renaming them, I just cannot get through editing a non-editable file,

[mjfarrell]

Dent, you've caught me away from home (typical) and on the road AWAY from my last living installation of Land Desktop.
However, I think you may be able (or I have done) what you are trying to accomplish without over writting anything.
When I get to the office where the C3D training is happening, I will see if they have LDT installed, run a test or two and report back to you. 

The good/bad news is C3D handles multiple Description Keys, and Figure preferences with relative ease.

[mjfarrell]

OK from the KB:


Issue


You want to create a Figure Prefix Library that can be customized easily.


Solution


The Figure Prefix Library is referenced by all projects. The Figure Prefix Library is stored in the default prototype fig_pref.db file, which is in the \data\survey\ folder. If the fig_pref.db file does not exist, it is automatically created from the default prototype fig_pref.txt file found in the \data\survey\lng\ folder.
...
...
...
Changes to the fig_pref.db file do not affect existing figures, only newly created figures.


So you may need to set up a figure prefix that is local to one machine for this work, or...
you may want to place multiple figure prefixes in seperate folders under the directory as shown above....

the hassle with this work around is that you will need to reset the path to the correct figure prefixes per project or they will grab the wrong ones...


OR if you create the correct fig prefs in your prototype(s) as advised in the first post....then any projecct created from the proper prototype should behave exactly as you desire. Although you will still want to verify that these special projects are pointing to the correct figure preference prior to processing the data.

[Dent Cermak]

That's what I was running into. Oh well, new software solves the problem. Another tool I can use to get them to spend the bucks!! I hope!

[mjfarrell]

yes it is a bt of a hassle...however not too difficult...

and a similar issue will come your way with setting the 'working folder' for your survey database(s) in C3D....you win, you loose... :ugly:

[BuckoAk]

Is is possible for more than one user to edit the figure prefix library at one time?, this could be done in C3D 2009.
Is this a settings issue or just how the new database is setup?

Thanks for any input.

[mjfarrell]

Is is possible for more than one user to edit the figure prefix library at one time?, this could be done in C3D 2009.
Is this a settings issue or just how the new database is setup?

Thanks for any input.

maybe.... what happens when you try?

you will have need to moved the location of yours to the network instead of the local All User Survey folder....Sounds dangerous...having two people working in that file at the same time

[BuckoAk]

Sorry I guess i got ahead of myself, The problem is that once one of us opens up cad it becomes useable only to the first person that opens cadd. Anyone else opening cadd that is trying to reference the figure prefix library will get an error saying file all ready in use.  So for now only one person at a time can bring field files into their drawing at a time.  Then have to close down and let the another person reopen cadd for them to use it.

[mjfarrell]

you might be able to defeat this 'feature' with user permissions (run as admin) ..off to investigate...

since I can't check your network user and file permissions...be sure everyone has adequte permissions to view/modify as required and test