Notifications
Clear all

Q - Carlson / Associating CRD file w/ DWG

6 Posts
4 Users
0 Reactions
2 Views
(@6th-pm)
Posts: 526
Registered
Topic starter
 

After setting the CRD with the DWG

- Points/Set CooRDinate File
- Points/CooRDinate File Utilities

and after saving the DWG file, closing the file and re-opening the DWG the association with the CRD association is gone.

This has been a minor irritation from day one and I just lived with it.

I'm now trying to figure it out.
Any help would be great.

Thanks

 
Posted : July 21, 2010 7:47 am
(@snoop)
Posts: 1468
Registered
 

CALL CARLSON - IT SHOULD NOT BE DOING THAT

Attached files

COGO FORMULAE.xlsx (83.5 KB) 

 
Posted : July 21, 2010 7:56 am
(@ladd-nelson)
Posts: 734
Registered
 

As a CRD association is made to a drawing, the information would be written to a *.INI file and would contain a line that resembles the following:

Carlson 2010 and later:
PROJECT=$PROJECTPATHMyCRD.crd

Carlson 2009 and earlier:
PROJECT=C:MyProjectPathMyCRD.crd

The name of the INI file would match that of the DWG and needs to be in a location that can be written by the software and operating system.

If you'd care to send me a copy of the DWG, its INI and the CRD along with the software version you are using, I'll be happy to take a look.

--
Ladd Nelson

 
Posted : July 21, 2010 12:49 pm
(@merlin)
Posts: 416
Registered
 

I have always had the same problem. It seems to come and go.

 
Posted : July 21, 2010 12:55 pm
(@6th-pm)
Posts: 526
Registered
Topic starter
 

Ladd,

I see the C drive reference.

If the files are saved to a network server drive and opened on a work station, would that confuse the DWG / CRD association when opened by another work station?

 
Posted : July 21, 2010 7:20 pm
(@ladd-nelson)
Posts: 734
Registered
 

It could potentially cause a conflict (this is one of the reasons Carlson adopted the approach cited in the 2010 version).

If User "A" is opening and using files on the server and User "B" has files locally and both users are using Carlson 2009 and earlier, drive mapping conflicts will likely result.

If User "B" is sharing his project folder (his local "C:" drive) with User "A" (his network drive), the solution is to have User "B" use the same drive map as User "A".

I know it sounds like a lot of alphabet soup but consistent drive mappings within an organization can save a lot of headaches.

--
Ladd Nelson

Attached files

 
Posted : July 22, 2010 8:57 am