Safekeeping vba code
I have nearly finished a program I will be installing it as .ACCDE myself into pcs for different customers for a tiny bit of yearly charge, the program will freeze and become unusable every 14 month, enough time for me to reinstalling it for a fresh new term, I have no problem with that, the tables are always backed up in a hidden folder.
But what worries me if any customer gets use of EverythinAccess and convert it back to .ACCDB then anybody with little knowledge with vba can change and play with the code and I will end up with no control of the program and I lose my all hard work.
Anyone can suggest anything for adding more security; I'm not really a programmer I made this program by teaching myself and collecting pieces of codes of the internet.
But what worries me if any customer gets use of EverythinAccess and convert it back to .ACCDB then anybody with little knowledge with vba can change and play with the code and I will end up with no control of the program and I lose my all hard work.
Anyone can suggest anything for adding more security; I'm not really a programmer I made this program by teaching myself and collecting pieces of codes of the internet.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Roy Cox
It doesn't help publishing the name of that software on a public Forum!
@Roy_Cox
It's not software. There is no known way to decompile an accde or mde file.
All they do is rewrite the file based on it's functionality.
It's not software. There is no known way to decompile an accde or mde file.
All they do is rewrite the file based on it's functionality.
I guess Access is not the proper Vehicle for that. You need an executable project something that will give you an .exe VB could be a good example. That is in my view of things.
gowflow
gowflow
@gowflow
A VB exe can easily be decompiled revealing the source code (assuming you mean VB.Net). Access, in this specific aspect offers more security, as the source code cannot be recovered. It can be reconstructed by extremely experienced programmers and that is what EverythingAccess does.
A VB exe can easily be decompiled revealing the source code (assuming you mean VB.Net). Access, in this specific aspect offers more security, as the source code cannot be recovered. It can be reconstructed by extremely experienced programmers and that is what EverythingAccess does.
I mean vb6
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks to every one commented on this topic, every comment was indeed useful, my main concern was only about "EverythingAccess", what is really interesting is the comment by MacroShadow in regard to the "Legal & ethical restrictions " that gave me peace of mind,
anyway what I'll do, I'll make it easy for them to contact me if they get access to my project, as well I will look at www.logicnp.com as mentioned in the previous comment
anyway what I'll do, I'll make it easy for them to contact me if they get access to my project, as well I will look at www.logicnp.com as mentioned in the previous comment