AutoCAD 2004/2005/2006 DWG Format

[#1]

In Summary :
1- YES for a R-O DWG password protected
2- YES for a DWF possibility to insert and view in Autocad
1- This is Funny, everybody (30 messages) thought about something we have to export or email to.
But the most important thing is the internal security
Imagine you have a details library
You want your users to insert them "as is", and no time to control the details.
So YES READ-ONLY DWG = (READ ONLY Wblocks)
FANTASTIC, I am waiting for that for years, I tried the Minsert but with the "REFEDIT" (since Autocad 2000) I have to rewrite my security developpement.

2- for DWF it will be nice to have it inserted and viewable in DWG file b/c its light vectorial size.

kaled.houhou@lessardgroup.com
www.lessardgroup.com
CAD Developper&Manager
703.770.3590 direct

[#2]

Since I'm the guy that started the first thread, I guess its about time I
threw in my two cents.

I wanted to see the ability to XREF a DWF file.
My main thinking was that this would be a "super-Bind".
One file we could distribute (internally or to consultants) and not have to
worry about dependent drawings.

"Wayne Fisher (Autodesk)" wrote in message
news4258B6F5BF42DE5AF1166D1311EF0FE@in.WebX.maYIadrTaRb...
> As a follow up to the earlier "DWF as Xref" thread:
>
> Which feature would be more valuable to you?
>
> [ ] Import (or xref) DWF into DWG (assume that the resultant graphics
would
> be viewable, but not editable)
> [ ] Truly "Read only" DWG (i.e. not just an OS read only flag, but a
truly
> "locked" DWG that could be viewed, but not edited without a password)
>
> and why?
>
> Thanks
>
>
>
>

[#3]

Truly "Read Only" DWG would be more suitable to our needs.

As Steel detailers we develop virtual 3D models that we co-ordinate the
steel fabrication, service ducts, concrete structures, glazing etc etc. We
do this so it elliminates construction head aches and most problems are
solved prior to the construction phase. BUT sometimes clients request the
models be sent to them, most of the time without any extra payment. So if we
were able to lock these files, they could utlilse them for the present job
but could not be editted for future projects, without additional release
payement or engaging our services for the future work, and hence protects
our long term existence as a company, instead of giving information away for
free.

"Wayne Fisher (Autodesk)" wrote in message
news4258B6F5BF42DE5AF1166D1311EF0FE@in.WebX.maYIadrTaRb...
> As a follow up to the earlier "DWF as Xref" thread:
>
> Which feature would be more valuable to you?
>
> [ ] Import (or xref) DWF into DWG (assume that the resultant graphics
would
> be viewable, but not editable)
> [ ] Truly "Read only" DWG (i.e. not just an OS read only flag, but a
truly
> "locked" DWG that could be viewed, but not edited without a password)
>
> and why?
>
> Thanks
>
>
>
>

[#4]

I prefer BOTH.

* DWF for internet issues where you need more security. So Xref with DWF contains no information but lines and colors.
* DWG for exchanging issues where information about several objects is still needed.

I hope to see this kind of functionallity in the next extensions?

Regards,

Edward Winter

[#5]

I would say "Read Only" because at some point, SOMEONE has to go through the effort to create a DWF every time the main XREF drawing has changed. All it takes is someone to submit an older version of the DWF to the client and/or sub-consultant which would rseult in someone being out of the loop.