TheSwamp
CAD Forums => CAD General => Dynamic Blocks => Topic started by: Bethrine on January 19, 2015, 10:59:56 AM
-
Okay, I have a block set up for a title block with attributes so, of course, I used the "Create Date" field in the drawing date box. It shows the wrong date. :blink: How do I correct this? Or should I not use a field in this instance? Once the creation date is there, I don't want it to change every time the drawing is opened or modified. It needs to be permanent.
Of note: this is my first time using fields and attributes. :evil:
-
Just a guess but is "Create Date" the date the block was created?
-
I think create date is day drawing is created?
-
I would say don't use a field if you don't need it to change.
-
Field and drawing were both created today. :?
I would say don't use a field if you don't need it to change.
I can do that but I was hoping I could just open the drawing and the date would be set. (Laziness).
-
or use the plot date or save date...
-
or use the plot date or save date...
Neither of those are permanent though. I think ronjonp is right. Maybe a "Save As" date could work?
-
Around these parts we have the line work and any static info (client name, address, project name, date issued, etc...) in a title block drawing that is then xref'd into the drawings that get plotted. There is a separate block with attributes that gets inserted into each drawing that contains things like drawing scale, drawn by, checked by, drawing name, drawing number, etc... for things that vary from one drawing to the next within the project.
-
Around these parts we have the line work and any static info (client name, address, project name, date issued, etc...) in a title block drawing that is then xref'd into the drawings that get plotted. There is a separate block with attributes that gets inserted into each drawing that contains things like drawing scale, drawn by, checked by, drawing name, drawing number, etc... for things that vary from one drawing to the next within the project.
Used to use a similar approach prior to Sheet Sets and Fields,
Title Block with Project data (static) attributes as XREF
Sheet Data (block) with attributes with sheet specific data.
However with Fields and Sheets sets filling in the Project Data is now largely automatic, there is little benefit to doing it that older method any longer.
-
We have small drawings here. What's happened is they've been overwritten as revisions for newer projects and older projects still in existence no longer have an accurate drawing or, in some cases, no longer exist or can't be found. I wanted the date field to be automatic and static...and I'm lazy. :whistling:
"I'm so lazy I do everything right the first time so I don't have to re-do it." ~my Dad :-D
-
We have small drawings here. What's happened is they've been overwritten as revisions for newer projects and older projects still in existence no longer have an accurate drawing or, in some cases, no longer exist or can't be found. I wanted the date field to be automatic and static...and I'm lazy. :whistling:
"I'm so lazy I do everything right the first time so I don't have to re-do it." ~my Dad :-D
OK - then use Drawing Properties add your special date information there....
-
OK - then use Drawing Properties add your special date information there....
This looks like a good idea for the original question.
The easiest solution would be to NOT use a field, and just fill in the attribute with a date, but you mentioned they get updated or overwritten.
And so this approach adds another line of defense with a custom field, that won't get updated automatically.
That's not going to stop someone from wiping out the field and typing in a date though..
-
OK - then use Drawing Properties add your special date information there....
This looks like a good idea for the original question.
The easiest solution would be to NOT use a field, and just fill in the attribute with a date, but you mentioned they get updated or overwritten.
And so this approach adds another line of defense with a custom field, that won't get updated automatically.
That's not going to stop someone from wiping out the field and typing in a date though..
It is tough to defeat stupid.
-
Around these parts we have the line work and any static info (client name, address, project name, date issued, etc...) in a title block drawing that is then xref'd into the drawings that get plotted. There is a separate block with attributes that gets inserted into each drawing that contains things like drawing scale, drawn by, checked by, drawing name, drawing number, etc... for things that vary from one drawing to the next within the project.
I think I am beginning to understand this better... :grumpy:
I also don't think I have the authority to do what needs to be done. :cry:
So this will be me for a while longer: :shifty: and hopefully not this: :rip: because it seems though they ask for this :idea: they don't like it. :uglystupid2:
I was trying to make my titleblocks fullproof but after thinking about it I probably shouldn't unless I get mgmt. approval.
-
Around these parts we have the line work and any static info (client name, address, project name, date issued, etc...) in a title block drawing that is then xref'd into the drawings that get plotted. There is a separate block with attributes that gets inserted into each drawing that contains things like drawing scale, drawn by, checked by, drawing name, drawing number, etc... for things that vary from one drawing to the next within the project.
I think I am beginning to understand this better... :grumpy:
I also don't think I have the authority to do what needs to be done. :cry:
So this will be me for a while longer: :shifty: and hopefully not this: :rip: because it seems though they ask for this :idea: they don't like it. :uglystupid2:
I was trying to make my titleblocks fullproof but after thinking about it I probably shouldn't unless I get mgmt. approval.
FOOLPROOF?
you are delusional
make something foolproof and you will discover a greater fool
it's not the same as building a better mousetrap...where all you will find is a dead mouse. :2funny:
-
make something foolproof and you will discover a greater fool
If what you mean by this is every plan should allow for change then I get it. Otherwise, please expound.
-
make something foolproof and you will discover a greater fool
If what you mean by this is every plan should allow for change then I get it. Otherwise, please expound.
Just when you think you have made it such that NO ONE will EVER be able to mess it up; some one will find a way to mess it up.
When ignorance gets started it knows no bounds.
Will Rogers
-
it's not the same as building a better mousetrap...where all you will find is a dead mouse. :2funny:
Okay, if that means what I think it means..I'd better not respond. :angel:
problem is everyone here would be in it me thinks. Any professional advice there?
-
it's not the same as building a better mousetrap...where all you will find is a dead mouse. :2funny:
Okay, if that means what I think it means..I'd better not respond. :angel:
problem is everyone here would be in it me thinks. Any professional advice there?
Whatever you decide to do....be fully prepared to offer a detailed (with pictures a 3rd grader can follow) tutorial
of HOW and WHY your system works and should be used. Otherwise, some clever fool will find a way to defeat whatever your system is designed to do, or prevent.
Then you will still need to visit with and educate all users about your solution.
I do this here, and still find users that want to 'fall back' to the old ways..... :yelling: :uglystupid2:
-
it's not the same as building a better mousetrap...where all you will find is a dead mouse. :2funny:
Okay, if that means what I think it means..I'd better not respond. :angel:
problem is everyone here would be in it me thinks. Any professional advice there?
Whatever you decide to do....be fully prepared to offer a detailed (with pictures a 3rd grader can follow) tutorial
of HOW and WHY your system works and should be used. Otherwise, some clever fool will find a way to defeat whatever your system is designed to do, or prevent.
Then you will still need to visit with and educate all users about your solution.
I do this here, and still find users that want to 'fall back' to the old ways..... :yelling: :uglystupid2:
mmmm. Okay. :D <edit> <-- that wasn't sarcastic <edit>
-
OK - then use Drawing Properties add your special date information there....
This looks like a good idea for the original question.
The easiest solution would be to NOT use a field, and just fill in the attribute with a date, but you mentioned they get updated or overwritten.
And so this approach adds another line of defense with a custom field, that won't get updated automatically.
That's not going to stop someone from wiping out the field and typing in a date though..
It is tough to defeat stupid.
You are correct, I've heard it said that a first line of defense "will only keep out the honest people".
So yea, some dumb cad user will go "hey, what's this grayed-out text mean? oh well whatever.. I'll just type in what I want"
(LOL)