Hi
I want to protect my model against being read, while still making it possible to be run from Excel VBA DLL without the password that protects the model or eventually with another one. If I protect the model and make a published model from the binary file protected, it asks in Excel the password.
Regards.
JJ
protecting a model while making it possible to be run
-
- Super Administrator
- Posts: 4590
- Joined: Wed Mar 05, 2003 3:10 am
Re: protecting a model while making it possible to be run
When you publish, you can set which versions of Vensim can actually open the model. Would that give you enough protection?
Advice to posters seeking help (it really helps us to help you)
http://www.ventanasystems.co.uk/forum/v ... f=2&t=4391
Units are important!
http://www.bbc.co.uk/news/magazine-27509559
http://www.ventanasystems.co.uk/forum/v ... f=2&t=4391
Units are important!
http://www.bbc.co.uk/news/magazine-27509559
Re: protecting a model while making it possible to be run
Hi
I want that the user may not read the open whatever the version he uses, unless having a password.
But he may use the published model via Excel VBA with or without a password. But if it needs a password, it is only to run the model, and not to read it.
To resume, I want to keep the source code secret whatever Vensim version is used , while making it possible to use it, via Excel for instance.
Regards.
JJ
I want that the user may not read the open whatever the version he uses, unless having a password.
But he may use the published model via Excel VBA with or without a password. But if it needs a password, it is only to run the model, and not to read it.
To resume, I want to keep the source code secret whatever Vensim version is used , while making it possible to use it, via Excel for instance.
Regards.
JJ
Re: protecting a model while making it possible to be run
The encryption in Venapp and the redistribution kit will do this, I think. As for Microsoft Office, it's not strong encryption (a dedicated sneak can break it), so deleting the diagrams might be an additional precaution.
/*
Advice to posters (it really helps us to help you)
http://www.ventanasystems.co.uk/forum/v ... f=2&t=4391
Blog: http://blog.metasd.com
Model library: http://models.metasd.com
Bookmarks: http://delicious.com/tomfid/SystemDynamics
*/
Advice to posters (it really helps us to help you)
http://www.ventanasystems.co.uk/forum/v ... f=2&t=4391
Blog: http://blog.metasd.com
Model library: http://models.metasd.com
Bookmarks: http://delicious.com/tomfid/SystemDynamics
*/
Re: protecting a model while making it possible to be run
Hi
Thank you for the information.
I did not think about protecting the VBA code.
Regards.
JJ
Thank you for the information.
I did not think about protecting the VBA code.
Regards.
JJ
-
- Super Administrator
- Posts: 4590
- Joined: Wed Mar 05, 2003 3:10 am
Re: protecting a model while making it possible to be run
Make sure you publish your model with a toolset that only contains those tools you want the end user to be able to access. And make sure it can only be opened by the Vensim DLL. This gives a basic level of protection.
You can also password protect the VBA, but I'm not sure how this is done.
The only other option would be to go for the redistribution kit as this allows you to encrypt the model. You would also get your own copy of the Vensim DLL that only you can use, this makes it much more difficult to get at the model.
You can also password protect the VBA, but I'm not sure how this is done.
The only other option would be to go for the redistribution kit as this allows you to encrypt the model. You would also get your own copy of the Vensim DLL that only you can use, this makes it much more difficult to get at the model.
Advice to posters seeking help (it really helps us to help you)
http://www.ventanasystems.co.uk/forum/v ... f=2&t=4391
Units are important!
http://www.bbc.co.uk/news/magazine-27509559
http://www.ventanasystems.co.uk/forum/v ... f=2&t=4391
Units are important!
http://www.bbc.co.uk/news/magazine-27509559