>>>>"And how do you detect if someone copies a file, then does a save as on the copy and should this come from the total save as...?"
>>I was thinking of some kind of randomly generated UID embedded in the PDF metadata (by RE) which interacts with the individual computer & still adheres to the set limit - could that be done?
And what about if they copy it to another computer?
By tree I mean the different branches of the same file (say someone does Save As twice from original document, producing copya and copyb)... if the limit was stored in the document, then the tree would look like this (save operations remaining shown in brackets)
doc (5 remain)
/ \
/ \
copya(4) copyb(4)
| |
| |
copya(3) copyb(3)
if the limit was stored on a server, it would look more like:
doc (5 remain)
/ \
/ \
copya(4) copyb(3)
| |
| |
copya(2) copyb(1)
Anyway, either way, to the best of my knowledge it's not something that you can achieve with Reader Extensions (it just turns on some Acrobat features in Reader, but doesn't allow limits on how often those features are used), but the method shown in the second diagram may be possible using Rights Management ES.
>>>>"Does the save operation become disabled when the limit has been reached too?"
>>Yes, but the user is pre-warned of this event...somehow!
There might be a better way, but if you did use a server based permissions system like Rights Management, you could probably write a quick web service, and do a look up on the PDF form to query the number of save operations remaining.