After reading a couple of threads, I have the idea that to deploy a front end with some level of security against tampering, the runtime version should be used. However, I am left with dealing with a security warning from Windows every time I open it. To deal with this, it seems I need a digital certificate. After reading Galaxiom's posts on this subject, it sounds like a lot of work to go through to get this done.
Does it cost anything to create a certificate?
Is the trouble of creating a certificate worth it? Granted, for 40 something users, it costs us whatever MS charges in annual licensing fees.
So, what would be the best option - use runtime or not? (If I understand the situation clearly enough)
And if I were to use runtime, in simple terms, how would I go about creating a certificate and deploying it with my front end? (I got lost in some of the domain/group policy stuff.) Plus, I am on the active directory as a regular user (if that's what we are called) with no special permissions or server access. I could ask for server access, if I need it. Do I need it?
Even using accde files, Windows still pops up a security warning.
Thanks.
Does it cost anything to create a certificate?
Is the trouble of creating a certificate worth it? Granted, for 40 something users, it costs us whatever MS charges in annual licensing fees.
So, what would be the best option - use runtime or not? (If I understand the situation clearly enough)
And if I were to use runtime, in simple terms, how would I go about creating a certificate and deploying it with my front end? (I got lost in some of the domain/group policy stuff.) Plus, I am on the active directory as a regular user (if that's what we are called) with no special permissions or server access. I could ask for server access, if I need it. Do I need it?
Even using accde files, Windows still pops up a security warning.
Thanks.