![]() It belongs to the company that hired you to do the work. That means that the intellectual property is not yours anyway. But, you can still do it if IT security doesn't care, you just need to use the Environ("UserName") to lookup who is logged in if you are not using that ID as the login already.Ĭlick to expand.As I said, this was for MY convenience for an internal application. It is one thing to use it at home for your convenience where no one else has access to your PC, but in an office environment, I wouldn't do it. This is a security breach and most companies would frown on it. In this case, I have legal agreements but it still comes down to trust. accdr prevents accidents but since NOTHING actually secures the FE, I don't bother for in house applications.įor applications I sell, I do all the things that are recommended because I am attempting to ensure my intellectual property. ![]() You might as well trust them to not mess around. You are trusting your employees with the company's most precious asset - its data. ![]() When they get access to the app, they are all informed that they are to use the interface provided and to never, ever try to break in to get around security. That ensures that the user has to go out of his way (and know the trick) to get into the FE. In fact, for my own convenience, I distribute as. We lock the FE to prevent accidents more than anything else. However, as CJ pointed out, NO Access FE or BE for that matter is actually secure. accde is just one more hurdle for the user to get past. accdr as the final step after creating the. Ultimate user will still need a full or runtime version of access installed to run a. If you need them, you will need to write your own equivalents. Main features missing from runtime - navigation window, right click menus, error handling - any error will cause the app to close without warning and without any useful error message, and minimal ribbon options. ![]() If you haven't already done that, you need to do so before distributing. accdr extension is to enable a developer with a full version to test an app that will be run in a runtime environment. The runtime files are quite large but should fit on a usb without any problem.ĭoesn't really matter, the. I would investigate using an installer (I use Inno) to install everything so your user only needs to execute an install.exe file - subject to any IT restrictions that may be in place. You should be able to download the runtime install files to copy to a usb for them to install ms access runtime. accde is the earliest version relevant to your users - they may have access 2013 installed for example, so your. They also need to have the same 'bit' (32 or 64) for a. Not sure what you mean by MSA (Microsoft Access?) but a user cannot have a full version and a runtime version installed, they will get conflicts. ![]() Click to expand.doesn't really matter, the. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |