Protect Excel worksbooks from being used after a certain time?

[gjjh25]

I work as a freelance estimator, and either use my own spread sheets or create new ones, that I own on other peoples computers.

Is it possible to protect these sheets somehow, So I and anyone else can use them whilst I am working there, but once i have left they can no longer use them.

So perhaps have a one month limit on the use of a spread sheet that I can re new as and when required?

Also it would have to be capable of stopping someone just copying the spread sheet and saving it and using it under a different name.

Could it be something that i could add to my spread sheets?

Your thought would be appreciated

Regards

Graham

[mojo249]

Add the first code to the Workbook_Open event. You can set a password on the VBA Project to prevent users from viewing/amending the code.

If security is really important you should also add the Workbook_BeforeClose code at bottom to protect the workbook when it's closed. This will prevent the user from overriding the Workbook_Open code by disabling macros.

Please Login or Register  to view this content.

Please Login or Register  to view this content.

[royUK]

That would only work if macros are enabled. You have very little chance of doing this because of Excel's poor security

Also, is ethical? You are employed & presumably paid so why should they not use the workbooks.

[gjjh25]

That would only work if macros are enabled. You have very little chance of doing this because of Excel's poor security

Also, is ethical? You are employed & presumably paid so why should they not use the workbooks.

A fair point, however, I am employed on the basis that they can use my knowledge and systems and spreadsheets whilst I am there and they are paying for it.

There are spread sheets that i use whilst I am working for someone which i have no problem of them using, it is just there are one or two that use my experience and knowledge that i dont want using.

[john55]

I had the same problem in the past. I spent many days to find a solution for users not to "destroy" the data by changing something. so, the easiest way I found was to let them to do what they wanted without "repairing" the file. after that they were very angry that the file was not working as usual or anymore.
so, I expalined'em what was the problem and the final "solution" was to protect the workbook so they use it without any problem (using the userforms and according to my "instructions") and their work is not saved (is not necessary) and I use a logfile to see who saveas the workbook.
from now on , the users will pay a much more attention at their "file" .

[Steffen Thomsen]

The safest way, if they are not to be used, Is to delete them when you no longer work there!

[gjjh25]

The safest way, if they are not to be used, Is to delete them when you no longer work there!

True, but I work at some places on an as and when required basis so I don't necessarily know my last day. So if I mam not there for a few days I dont want them being used in between my visits.

[Steffen Thomsen]

If you are at a place where they dont know vba, then have a look at this

http://www.cpearson.com/excel/EnableMacros.aspx

Another option, if the files are on a shared network is protecting the placement folder instead of the file!

[mojo249]

That would only work if macros are enabled. You have very little chance of doing this because of Excel's poor security

That's why I suggested the Workbook_BeforeClose code. If its protected each time the file is closed then it will still be protected if the user disables macros.

[gjjh25]

Add the first code to the Workbook_Open event. You can set a password on the VBA Project to prevent users from viewing/amending the code.

If security is really important you should also add the Workbook_BeforeClose code at bottom to protect the workbook when it's closed. This will prevent the user from overriding the Workbook_Open code by disabling macros.


[CODE]Private Sub Workbook_Open()

Thanks for this, so do i open vba and insert this as a new module, not very familair with vba.

Regard

Graham

[royUK]

Please don't post whole posts