Hi guys,
I am finding a way to secure my BE on the server, sooner or later they will find a way to extract information w/o the use of my application and will cause more problems.
I tried to put a PW on the BE but everytime I connect on the BE it prompts me a PW, sorry I am a newbie.
your help is much appreciated.
Thanks.
Hi
I have split my DB, FE & BE. The BE is located on a network drive and the FE is located on several local network drives for staff to use. Once I created a password for the BE, the main form would not open for the user on the FE. How can I secure the BE so the data can't be opened.
Thankyou
Garry
I would like to secure my database (ha ha...at least to some extent).
Here is the basics...
When someone comes into the database I can identify them as they enter by using "Environ("username"), this gives me a unique number for that user ("R54436") (I am on a system called "Citrix" with FE/BE) and from there I would like to:
1.) let them in or not let them in
2.) direct them to particular areas based on who they are
3.) deny access to certain areas all together
I have a table in which I have all users "R" number along with name, user level (1,2 or 3) and the branch office number and can add other info if needed.
I have a form that loads before anything else (invisible) that captures the users "R" number.
I guess I am just not sure how to compare the "R" number that I capture on the invisible form with the "R" numbers in my table. Ultimately once I find a match I would like to populate the invisible form with that users values from the table so I can reference those values throughout their vistit.
Any pointers would be great.
Hey
I am looking for a way to secure a single DB. I would like to be able to use the DB on other PC, but still have user control.
I have found that when using the MS Access User and Ground way will only secure DB's used on the PC it was set on. If i take the DB to my home PC i am not promted for a Password and i can go mad with information i would like to protect.
Am i doing something wrong when setting the security? :confused:
Shot
Hi all.
I know Access security has been discussed ad nauseum in these forums and that there is a wealth of information in the archives, nearly all of which I have read often.
And I have a small question.
For years I produced applications which didn't need tight security. However, I tried to stay well informed on the matter.
Security is important in this project. I secured a database properly, as well as I can determine. I then made a copy and deleted all the tables in the one which will be the frontend and linked to the tables in the copy which will be the backend. Only Groups had permissions, individual Users, none. Life was good.
Then I did something, not sure exactly what. The end result is that the frontend seems fine; I cannot open it unless attached via the .mdw I created specifically for this project.
The backend, however, I can open even when attached to the system default .mdw.
Can anyone tell me what I've likely done, and how I might nail down the backend once again?
How do I secure my database so no one can install it on other computer
I know I can make the MDE file, but any one can use it.. is there a way to create a installation setup so it needs a serial o something like that.. if so what do I have to do?
I don't want my database to be installed unless I provide the authorization
I'm almost finished software, and I have to deploy now.
I'm wondering, what is the best way to secure software ?
Is MDE secure enough ?
Or, is it possible, just like in VB , to create "dll" file, and to put code in dll file,
and call it from forms, reports ?
thanks in adv
I have already used the option in the 'Startup...' menu so that the user only sees the database window with the tables, queries and reports etc. But the user can still press the 'Design button' in the database window. And especially for my queries and reports that would be a problem if they altered things in there by accident.
Is there a way to secure this? Can I hide the queries but still let the user access one table and the reports?
I have tried to search for answers and the runtime command removes everything so that nothing is visible :p
Hope You can help :)
Im unable to create an MDE file, access keeps trying and then saying that its unable to create MDE.//// Is there any other way that I can secure both my codes, forms, modules and macros from being imported into another database since I cant create the MDE file?
View 6 Replies View RelatedHello All,
I was wondering if it is possible to connect a MS Access front end to a MS SQL server on the internet in a secure way through ODBC or some other means.
Anyone have any ideas?
Thanks.
My program is finally complete, much thanks to everyone here that helped me!
Here's (hopefully) my final issue:
I haven't actually tested this yet to see if it's an actual issue, but I assume it might be. The program i just built needs to be transferred to my client's computer. currently my program consists of three files: PROGRAM.mdb (interface), DATA.mdb (linked tables), PROGRAM.mdw (security file). they are in their own separate folder (C:Program) and play nicely together. i'm concerned because i think that once i zip it up and email it over, when my client unzips it into a folder on his hard drive (named c:program so he doesn't have to re-link them), it might not work because of the .mdw file. if anyone recalls my thread entitled "H E L P ! ! ! !" you see why I'm concerned.
should this just run without a problem, or do i need to have him do all sorts of steps to reassemble the program?
usual lifesavers? i love you guys
Thanks
-Jason
I have Access 2003 in my computer and I have developed an application which I want to share with my co-workers. But they have only Access 2000. Since MDE is only in 2003, I had to convert my 2003 application to 2000. Is there a way to secure 2000 application? I dont want anyone to change my code or import or read my code..I am not sure what is possible..Could someone please tell me how I can do that?
Thanks.
I just post this one because it took me more than an hour to find a comfortable solution for access 2003
http://support.microsoft.com/default.aspx?scid=kb;en-us;826765
To set the AllowBypassKey property to False, follow these steps: 1. Start Access.
2. Open an Access database project.
3. In the Database window, point to Macro on the Tools menu, and then click Visual Basic Editor.
4. In the Visual Basic Editor, click Immediate Window on the View menu.
5. Type the following code or paste the following code in the Immediate window, and then press ENTER.CurrentProject.Properties.Add "AllowBypassKey", False
6. Close the Visual Basic Editor, and then close the Access database project.
7. Open the Access database project. Try to bypass the startup options that are set for the Access database project by holding down the SHIFT key while you open the Access database project.
The functionality of the SHIFT key that permits you to bypass the startup option is disabled. Although you hold down the SHIFT key to bypass the startup options, the startup options are executed. You cannot bypass the startup options.
I am kinda new to 2007 and have at the moment a simple database.
I want three things
A: Use the database on a server.
B: Restrict the use to users etc as i used to be a ble to do in Access 97 i think (do i have to make a MDW if so how ?) 9I tried ACCDE but does not seem to do anything)
C: When users use the datavase not see all the normal access editing stuf..
Steve
This morning I accidently ran the "User-Level security wizard" on a secure database that we use. I meant to add a member but clicked the wrong thing and followed suite by hitting "Finish" instead of cancel because I wasn't paying attention. Aside from creating a "Security.mdw" file which isn't being used at all, it also somehow managed to lock everyone but the administrator out.
I checked the Users/Groups and Permissions, they are all there and correct, nothing seems to have been changed at all but when anyone tries to log in now they get the following error:"You do not have the necessary permissions to use the '...mdb' object. Have your system administrator or the person who created this object establish the appropriate permissions for you."
I've read some posts with similarish issues that recommended recreating the .mdw file and importing the data over. The file is encrypted so I wasn't able to do that but I did try making a copy and renaming it then changing the path in the Access shortcut to the copy instead. What all files/settings handle this and if the Users/Groups show up correctly in the database, what could be preventing the users from getting in?
I've made an access project (ade) and stored the admin with password in the ade file.
When I open a new database I can use the import feature to import all tables with definitions and data from the ade file. All other objects are being locked.
How can i disallow tables from my mde to be imported into another access application?
I'm building an application in MS Access 2010.
This application must be able to read from a big table in a separate accdb.
This separate accdb contains info that should NOT be available for all my users to copy, as it is valuable competitive information that could be abused by people with bad intentions. So, a linked table solution is not an option.
However, it should be possible to run parameterized queries that do simple look-ups that return only small/relevant portions of the database.
How to secure SQL data when my MS Access database must access it using linked tables. Generally speaking on the Internet, assertions that migrating to SQL is more "secure" are rampant; explanations of just how that is are scarce.
Sure I can restrict access and put different roles on different tables, then put different people in those roles, but that doesn't really do me any good. Ultimately I want to achieve the following: Allow them to do all kinds of stuff (including Update, Delete, Insert) using my access application, but I would NOT want them to have those same rights if they installed SQL Server Management Studio, or for that matter, simply created an ODBC connection using another access or excel application.
In other words, ideally, I'd like to have SQL server view my Access application as a user in its own right. Not sure if that type of impersonation or identity is possible to achieve.
I have a question about sending secure emails by VBA code in MS-Access. I have a Access application within you also can also send emails by VBA code using outlook. Everything works fine, but now the recipient wants to receive the mails with a digital signature by S/MIME.
I got a digital certificate from the recipient as a pfx-file.
Is this possible in Access using outlook ?
I use MS-Access 2010 en Windows 7
I'm not sure which is the better of two options-
My problem is I need to make it easy for my users by authenticating themselves once when they open the database. User-level security is adequate for that job, but when I need to use the authentication information for connection string, I'm a bit antsy about storing it somewhere in Access, as I understand that passwords shouldn't be stored in the database itself (and as far as I can tell, it's not even encrypted or hashed!)
I am wondering if converting it to MDE would be sufficient to encrypt the password or will it still be apparent using a hex editor? I also know that Jet can try to use its own security to authenicate to the back-end, but not sure what I need to do to prompt Jet to pass along the credentials.
Alternatively, would it be better to somehow implement login using backend's security model, if even possible?
TIA.