dwg expiry

[x11start]

The solercy with which plannerroad and gp responded to me this morning.... has "galvanized" me!

Now I would like to ask them ... and all those of the forum, to find a solution for a problem ... that maybe could interest many:

by sending a file to a customer, or to the company that has to realize it. . you always run the risk that variants are not transposed: basically the first drawing sent....then it seems impossible to delete!

to this problem, long ago, on this same forum, I proposed a solution: insert into the useri1 variable (saved in the design to protect), a n. which represents the revision.
when another design is sent, with n top revision, the previous one is no longer displayed.
to get this I made a lisp (that allego) that (unfortunately) must be launched automatically at the opening of the design.... then must be inserted in the acaddoc.lsp file.

this solution was accepted... in misode by someone from the forum, who accused me of wanting to change the settings of others' cad.

At this point I ask myself: Could someone solve the problem without "doing damage"? Thank you.

 

[stefanobruno]

I don't understand anything about macro and lisp and I wonder:
instead of the opening block, you can't make it appear, on the old file folder, a watermark saying "design replaced by ... "?

Bye.

 

[fabioberta]

send it as dxf instead of dwg...
Usually this is used for drawings exchange

 

[stefanobruno]

send it as dxf instead of dwg...
Usually this is used for drawings exchange

thing c' enters with quello che says x11?

 

[Cristallo]

I have a different, logical problem, trying to explain it.
if I send a revision of the design, that design represents the last (hopefully) revision. the last design I sent, at least in hopes, is the final version, unique and unmistakable.
how do I then make invisible, with the last file sent, all previous versions of that same file (which are different files)?

perhaps in the field of x11 drawings have standard expiration (like milk, to understand us? )
the design, albeit good, must be revised within the xx-xx-xxxx?
otherwise does not make sense the date control of the file lsp. that says that if the date is "less a" you can open the dwg. but in purely theoretical online, the rev. x of a dwg is valid until the issue of the rev. x+1 (which may even never happen).

set a user variable makes sense in a dwg, in which it is saved.
If for any reason, I open the rev. x-1 of the dwg, in the dwg I will have a correct user value (for dwg).
I will probably have an incorrect date, but this will happen even if I open the rev x (final) after x years from the issue (out of the expected range)

On the other hand insert a user and a date directly into the general autocad files I see it unavailable.
a) you are likely to make any other design malfunctioning (other sources) that by chance uses a user variable that has the same name as the x11 user;
b) you should have so many user variables for how many designs of that supplier you own (maybe one is still at rev.2 another at rev 6...);
c) same address for the date....

What did I not understand?

 

[Cristallo]

instead of the opening block, you can't make it appear, on the old file folder, a watermark saying "design replaced by ... "?

I think the problem is identical to that of the disappearance of entities. . .

 

[dieva]

...to this point I ask myself: Could someone solve the problem without "doing damage"? Thank you.

I see it like this (I hope I understand your problem well):

Given that the only one who is aware of the latest revision of a design is who issues it, why, in these years of cloud and always active internet connections do not think of the following system?


a) on any website or web space who issues dwg files to each revision of a design updates a corresponding .txt file - having the same name as the dwg file - inserting the simple number of revs inside.
example: for the tav1234.dwg file there is on the web tav1234.txt whose content is a number, the number of the last rev performed.

b) the application to be supplied to the customer, and to be loaded for each design automatically, must only make this verification:
- search for an established web address the name of the .txt file having the same design name-
- read the content of the file and compare it with the value of useri1 (or perhaps other than those of the properties of the file).
based on the outcome of the comparison perform the planned actions (warning, cancellations, undefine command plot etc...).

the weak point is the possible lack of internet connection but also in this case the application can issue a warning, type "impossible to verify that the current design is the last revision issued!"

 

[x11start]

thank you for the answers, but I think I haven't quite understood my problem:

when I send a drawing by e-mail to an impresario, to a coperturist ... in short to any person who will then "physically" create the building; then it becomes difficult to "eliminate" a version that in the meantime has become obsolete due to variants or additions.
until a few years ago, when the drawings were sent in paper format.... was the "nature" itself that provided "destroy" the drawings (the rain, the sun etc); So he gave him a new copy of the design and everything ended there.
Today, thanks to technology, even the last of the contractors has an e-mail and a plotter that allows him to reprint infinity the design he received.....e (for an inexplicable mental tarlo!), is almost impossible to replace with new emails. in the sense that the latter are read... but then ignored!

my proposal, it was an attempt to make sure that if in the hard disk the design ver2 is saved.... version 1 reports that it is no longer updated.
that of the date then is a "fine" for the characters particularly "hard of cervix", that the e-mails after the first, ignore them completely. At that point you put this expiration on date, like bottle of milk! It will mean that, if the design doesn't change, he will be sent several times the same version... but at least I'll be sure he doesn't take that wrong!

all these elucubrations, were born exclusively to try not to find the wrong foundations.... with the omino that tells you: "but I followed your drawings!"

for paper drawings I should inform me about the things used by crouise tom in mission impossible .... who destroy themselves! Hehe...

 

[GP.]

It is certainly not an easy solution problem.

acaddoc.lsp is not installed with autocad but must create the user, I do not believe that the impresario or the coperturist do so, if you can then with the ex to install it the dieva solution seems to me the most elegant one.

another could be to distribute the dwg with a persistent reactor that is activated when you want to print, whose function must be logically written in aaddoc.lsp

education:
- verify if in the pc there is a dwg file with a suffix higher than the current dwg, e.g. xxxx_001.dwg, xxxx_002.dwg, etc.
- if the file exists the reactor does not allow plating and launch an alert type: design not updated, see xxxx_003 file place in folder dincopallo
- if the file does not exist the reactor allows the plotting

 

[QWAZ]

thank you for the answers, but I think I haven't quite understood my problem:

when I send a drawing by e-mail to an impresario, to a coperturist ... in short to any person who will then "physically" create the building; then it becomes difficult to "eliminate" a version that in the meantime has become obsolete due to variants or additions.
until a few years ago, when the drawings were sent in paper format.... was the "nature" itself that provided "destroy" the drawings (the rain, the sun etc); So he gave him a new copy of the design and everything ended there.
Today, thanks to technology, even the last of the contractors has an e-mail and a plotter that allows him to reprint infinity the design he received.....e (for an inexplicable mental tarlo!), is almost impossible to replace with new emails. in the sense that the latter are read... but then ignored!

my proposal, it was an attempt to make sure that if in the hard disk the design ver2 is saved.... version 1 reports that it is no longer updated.
that of the date then is a "fine" for the characters particularly "hard of cervix", that the e-mails after the first, ignore them completely. At that point you put this expiration on date, like bottle of milk! It will mean that, if the design doesn't change, he will be sent several times the same version... but at least I'll be sure he doesn't take that wrong!

all these elucubrations, were born exclusively to try not to find the wrong foundations.... with the omino that tells you: "but I followed your drawings!"

for paper drawings I should inform me about the things used by crouise tom in mission impossible .... who destroy themselves! Hehe...

send him a virus that finds him and destroys the old file

 

[numero1]

apart from the qwaz joke highlighted a real problem.......
If the hard cervix then a tomorrow will report you?
because what you're asking is to put you in another pc, and check if there's still another version of the same document.
Have you thought about this?

 

[dieva]

... that of the date then is a "fine" for the characters particularly "hard of cervix", that the e-mails after the first, ignore them completely. At that point you put this expiration on date, like bottle of milk! it will mean that, if the design doesn't change, he will be sent several times the same version.... but at least I will be sure that he doesn't take that wrong!...

the 'problem' date is easy to solve. you can create a cartilage with a fielddata with a diesel education that compares current date and expiry date and when you are beyond the expiry date writes a warning at the center of the sheet.
I have prepared an example. the expiration date is convenient to write it in userr1 so you do not change the diesel code

 

[QWAZ]

did you see these?http://www.armjisoft.com/?page=autocadownerguardhttp://www.cadlock.com/products/cadvault/http://www.summercad.com/eng/free4.asphave expiration date function

 

[c'erounavolta]

did you see these?http://www.armjisoft.com/?page=autocadownerguardhave expiration date function

there is the free version that also limits the number of prints, but the files cannot exceed 500kb

 

[Cristallo]

that of the date then is a "fine" for the characters particularly "hard of cervix", that the e-mails after the first, ignore them completely. At that point you put this expiration on date, like bottle of milk! It will mean that, if the design doesn't change, he will be sent several times the same version... but at least I'll be sure he doesn't take that wrong!

all these elucubrations, were born exclusively to try not to find the wrong foundations.... with the omino that tells you: "but I followed your drawings!"

you're trying to "noise" common sense. at this point it can be good to enter between the dates of your cartiglio oltra at the date of issue, a expiry date.
If the omino says "but I followed your drawings!" take the table he printed and show him that he expired.
only once, that the omino must repay the foundation of his pocket. the second will look at the "fall".

but, allow me, if you send me a dwg with an exe attachment, which creates an acaddoc.lsp (that maybe I already own for my needs), I will piss off and without opening it, I will send it back.

 

[PlannerRoad]

...but, let me, if I send a dwg with an exe attachment, which creates an acaddoc.lsp (that maybe I already own for my needs), I will piss off and without opening it, I will send it back.

condivido, precisely for this x11start had placed the question

.....: Would anyone be able to solve the problem without "doing damage"? Thank you.

 

[x11start]

you're trying to "noise" common sense. at this point it can be good to enter between the dates of your cartiglio oltra at the date of issue, a expiry date.
If the omino says "but I followed your drawings!" take the table he printed and show him that he expired.
only once, that the omino must repay the foundation of his pocket. the second will look at the "fall".

but, allow me, if you send me a dwg with an exe attachment, which creates an acaddoc.lsp (that maybe I already own for my needs), I will piss off and without opening it, I will send it back.

"aridaiie" crystal.... you already wanted me to stem for this idea!
possible that you can not find a solution ..... without "intruding" on someone's computer, putting a virus, making who knows....
my idea was just finding a way to avoid mistakes.... far from me the intention of doing illegal things!

 

[Cristallo]

my idea was just finding a way to avoid mistakes.... far from me the intention of doing illegal things!

x11, maybe I was misunderstood. I never thought you wanted to do illegal things. It's that coming from the good old dos, if you send a drawing with an attachment to an exe, a com or a bat, I'll automatically discard it, I don't even worry about understanding what the attached file is.

possible that you can not find a solution ..... without "intruding" on someone's computer, putting a virus, doing whatever. . .

I don't think there's any "standard" and transparent way.
a dwg is opened by a program that works as an "eye" (autocad) that looks at the card (the file).
You want to make sure my eye doesn't see the card under certain conditions. You can only do it if you give me a pair of ad hoc eyepieces.
a dwg can be opened by autocad lt (no lisp support), from nanocad, draftsight, a myriad of free cad and all verticals with autocad base. how do you establish the recipient as it opens (and then corrective countermeasures)?

"aridaiie" crystal.... you already wanted me to stem for this idea!

I don't want to change you.:frown: I think your problem is a false problem.
What sense do the revisions have if those who receive them do not look at them? But you can't solve this. a very colorful proverb (which eulcoro) reads: "You have voja to put ruhm, if he is galley, he never becomes a baba."
think of the legislators. they give you only the varied parts with the "revision" and they don't care to rewrite the whole law.
you rewrite all the law, and you do the problem that the recipient should not see the previous version?

in all this, I repeat the Prince concept: a revision is valid until the next, not until a certain date.
If you give me a revision and then you send me the last version that is the same as the previous one, I won't make mistakes, but I'll think that you work with the arm the grappa flebo... And that doesn't even sound good, does it?

 

[x11start]

I really liked the solution with the dieva "diesel" field: with a dwg prepared in that way, solves the problem of expiration with date.
Now it's a question of finding something similar to the review no...... "dieselisti" come forward! and thank you all for the interest!

 

[lattu]

probably the cloud route is the most suitable one, if it was denied downloading the file itself.
or you activate a cloud space and each file will be shared with certain people, obeying somehow to keep the file in the cloud (I don't really know if it is possible)
the overwriting by us of the file would automatically delete outdated versions.