Hi,
I have a database, which contains linked tables to another database. The information held in the tables are mostly open for every permitted user but some of the table informations are restricted to a few user only. To manage all of this different permissions I created a workgroup, changed all the necessary things to become an administrator and run the security wizard to secure my database. Finally I want to give every single group the access it belongs to. And there is my problem.
I have a form which has a VBA code underlying which selects data from a table and two queries and where the user can set individual criterias. For me as an admin user this form works perfect. When I log on as a user I can't find out how to set the permissions not to receive the error message: "You do not have the necessary permission to use the 'MSys Table' object...." The user should not be an admin user and I already set the modify, update, delete, read, read design permission to the group. Nothing helps.
Please if anybody has an idea what I can try I really would appreaciate this help!
Thanks very much :)
Every time I open a database, no matter than I've opened it before, it asks opening blalala.mbd maybe harmful to your computer. Is there some way to stop that message? I went searching around in tools customize and nothing.
I have read through the various posting regarding ACCESS 2003 security warnings. As like everyone else, I receive a security warning stating, “This file may not be safe if it contains code that was intended to harm your computer.” I have already installed Microsoft Jet 4.0 Service Pack 8 and I have already enabled sandbox mode. This warning still appears when I try to open databases sent to me by other people. It also appears when I try to create a new database from my own computer. I understand why this message may appear when I open other peoples’ databases, but why would this error message appear on my own computer after I create a database from the very same computer? I would like to market my databases to specific clients, but I need to eliminate the security warnings that would appear each time they opened my databases from their computers. I don’t want to suggest that people change their security levels to low in order to open my database. For this reason, I am considering the option of digitally signing my databases with an authenticated signature. As something like this would run anywhere up to about $400.00, I want to make sure that it would be the best, and correct, option for me. My ultimate question: If I am already trying to create databases from my own computer and receive this warning message, would a digital certificate work in eliminating the error message for my future clients? Also, I understand that I may use the signatures for up to a year. Would I be able to use this for multiple databases that I create as long as it’s within that one year, or would I only be able to sign one specific database and use that same database for the entire year? This is a bit of a pricey endeavor for me, so if there are any other options, I’d love to hear those, too. Thank for the help in advance!
Ok.. I have done this before at another job, but this network (or stupid me) is giving me trouble. I'm trying to setup a database security (login/password) for a database on a network. I setup the security levels..setup a seperate workgroup... From my computer it logins fine with the correct workgroup.
My db is secured using Access security but now find myself needing to code a little security work around if possible.
I have a form that has a subform. On the subform is a field named "Comments". The subform security only lets a particular group write to the fields it contains (including "Comments"). I have a new user that I need to allow to write to "Comments" but not to any of the other fields on the subform. I could make another subform with "Comments" only field and redo my security so that the original group can write to both subforms and new user can only write to "Comments" subform but I think it might be easier to code in that the new user is only allowed to write to field "Comments" in the existing subform. Every user logs into the db so I can get the user ID.
Am using the standard files ACCESSRT.MSI and ACCESSRT.CAB to install Runtime.
Does anybody know a QUICK way of supressing the annoying security messages which pop up, when the application starts under this configuration?
I don't want to write any fancy install wizards or scripts, just need a basic runtime install like the above method, but with "Low" Macro security set.
Either when copying from one db to another on my machine or running a db produced on that machine on a network, I get the message "the database has been placed in a state by user (my machine is called "Rat") that prevents it from being opened or locked". =Error 3734. The security data says I am "Admin" and permission is set for Admin and Users. It has been doing this intermittently for a while and now does it all the time. Follow up data All databases are created, revised and run on home machine (Rat) and run on the office network.
The offending DB will permit internal design, editing , copying and will accept pasting IN of tables etc. from other DBs. But it will not allow copying OUT of files such as a table to other DBs even on the machine that created them. However it will allow copying and pasting of objects such as forms in visual form or individual query cells to other DBs.
I’ve carefully compared the Tools/Security/User & Group Permissions with a good running version of the DB and can see no difference. Permission settings on good and bad DBs are:- Permissions: Admin Object: Current DB Checked: Open/Run, Open Exclusive, Administer. I’ve also checked each individual files’ Permissions. The .ldb file, viewed with Word with the offending DB running on my office machine (Weasil), reads:- WEASIL_ Admin_
The creating machine “Rat” uses the Account “Richard”: but I have had few similar problems before. While revising the DB, I made 30 copies of at each stage along the way but saved carefully each design change and certainly did not deboot the computer without doing so.
I’ve tried the above procedure on my computer (Weasil) at the office, but got the same result. So it’s not the computers or MS Access 2000 program. Somewhere along the line, perhaps, the DB got corrupted. It Repaired and Compacted OK but still has the problem.
I have a table in Access database. I would like to set read only permissions to some of the fields/columns in the table. I do not want user to alter or edit some fields/columns in a table. Could someone give a solution for this?
I've read and gone though quite a few of the scrips and examples for creating logins and security and i'm getting to the stage when i need to have good understanding of the different methods.
Some of the examples whilst create a user login do not really allow for security within the database whilst the build in security wizard would appear to offer that functionality.
I am thinking that I will use the Workgroup file and that method. My question is am i able to utilise the fact that if a person 'AdamA' logs onto the database which is built into the workgroup security file. am I then able to take 'AdamA' to populate a table which records actions by a user? (I can't seem to find any thread or book reference to doing this)
I have installed Microsoft Access 2003 and Microsoft Access 2003 Developer Extensions. I can create Access application by using the Package Wizard. But after I upgrade from Microsoft Access 2003 to Microsoft Access 2007. I can't use the Package Wizard.
I have two database applications and they are: - the (A) application is for administration use. - the (B) application is for normal users use.
the idea is that: I made the (A) application for administrators who have full control over the database objects (tables, forms, queries, and so on ...).
the (B) application I have created for normal users who will have only to use forms to insert some data and display data only.
but the two applications has a respective table called "vacation request" table. where I linked them, so the both administrators and users can share the data.
The real question is that: How can I prevent the users from seeing the database objects in their application. I used the database options which have helped me in hidding the database objectives when the users open the application, but unfortunately they managed to access to the database objects by pressing the special keys.
I would like to have an access to the (B) application when I want to make some modifications to the forms and then lock it from users where they only have to use the forms for requesting vacations and view the vacations.
I've been using the following code successfully in Access 2003 & now I need to migrate to Access 2010. The purpose of the code is to use the items that the user selects in the list box to build the criteria of a query. Access 2010 keeps giving me a syntax error when I try to run the query & I don't know why:
My code is:
On Error GoTo Err_Command151_Click
' Declare variables Dim db As DAO.Database Dim qdf As DAO.QueryDef Dim varItem As Variant Dim strCriteria As String Dim strSQL As String
[Code] .....
The syntax error I get in Access 2010 is:
Syntax Error in query expression 'SELECT * FROM qryContractListSummarybyDateContract3TYPEBREAK WHERE qryContractListSummarybyDateContract3TYPEBREAK.Rep ortableName IN('Adbri Masonry NSW');'
Attached is a screenshot of the relationships in a database I built a couple of years ago. It's worked absolutely fine in Access 2003 and currently has over 18,000 customers with associated information in it.
However, when I open the database in Access 2007 the performance is awful. All the forms are very slow to respond when tabbing between form elements. I've experimented by reducing the number of form elements calling on related data on a given page and whilst this improves performance it reduces usability - something I don't want to compromise on especially since Access 2007 should be able to cope with this.
My next question is therefore whether I've got the most efficient underlying table design and I can't see any other way of doing it than my current method so I'd be grateful for any feedback or advice anyone has.
I am working on a massave aplication that has been running in Access 2000, but recently several of the file sharing users have installed Access 2003 because of the limited availability of Access 2000. All the users are using the same file off the server.
The problem we are having is that when we reference a subform in the "[Forms]![FormName]![SubformName]![FeildName]" Access 2003 does not recognize it and returns an error. I have found that if I will modify it to "[Forms]![FormName]![SubformName].[Form]![FeildName]" it is recognized in both 2000 and 2003.
To try and change every instance of a subform reference will take forever and I am garuteed to overlook something. We reference subforms all over our program, missing any one of them would be a disaster. Before I went to the tedious task of looking through everything I just wanted to throw the situation out there and see if any of you had any great ideas on how to get it fixed efficiently. I would apreciate any ideas.
I upgraded a 2000 db to 2003 recently. When I ran the function below it gave me an error on the line in green. Any thoughts? Thanks. Const FIRSTROW = 13
Dim wsp As Workspace, dbv As DAO.Database, tblResolve As DAO.Recordset Dim tblVchs As DAO.Recordset, tblImpTmp As DAO.Recordset Dim ObjXLApp As New Excel.Application Dim FileToOpen As String, WhereCriteria As String, ImportTemp As String, tmpVch As String Dim TotalDupes As Integer, TotalGood As Integer, TotalRejects As Integer Dim TotalBlank As Integer, R As Integer, C As Integer Dim BadSheet As Boolean, ImpFail As Boolean Dim tmp, tmpType, tmpCtr, tmpRsn
If Forms![Import Block Vouchers]![Import Program] = "0" Then MsgBox ("You must select a Program to load.") ObjXLApp.Quit 'Exit from MS Excel Exit Function End If
I have an Access DB that I created in Access XP. It works perfectly when used in Access XP. When used in an Access 2003 environment some of the functions don't work anymore. I have users who use Office XP and users who use Office 2003. Does anybody know how to make this DB work in Access 2003 without having to do wholesale code changes?
I have already changed the security to "Low" to bypass the security feature built in in Jet 4.0 but it didn't help. I might have to uninstall Windows XP SP2 to make it work because I know that the application works in an Office 2003 environment with Windows XP SP1 only. But I'm trying to avoid having to uninstall XP SP2 because it's a pain. Any ideas would be greatly appreciated.
Thank you.
My workstation environment is as follows:
OS: Windows XP SP2 Office: Office 2003 SP1 Jet: 4.0
I've created a database in access 2003 with the default file format being Access 2000. Everything works fine on my computer and many others, all of whom are running different versions of access (2000, 2002 & 2003).
I have not had any problems with this database until recently and in the last few weeks we have had 2 users, both of them being Access 2000 users who have had the same problem.
The problem they are having is that when they click on any of the switchboard items, the buttons depress an then come back up again when the cursor is moved away, but nothing else happens - no action, no error message - nothing!!! Its the same for all of the buttons on the switchboard.
Does anyone know what is causing this? I have another computer with Access 2000 on it and this works fine, as it does on several other computers runiing Access 2000, I just cannot understand why it is not working on these 2 particular machine.......
I have recently installed access 2003 w/access 97 installed both are on my hard drive. When I create a new db in access 2003 it saves it in an access 2000 format. Does any one know why it does this?
I have two questions related to deplying an Access project I have been working on.
1. I started developing the project in Access 2000, but midway upgraded to Office 2003 and so the remainder of the project has been developed in Access 2003. Things seem to be fine, except that in the top most title bar, after the project name, there appears the following text:
xxxxx: Database (Access 2000 file format)
where xxxx is the name of the .mdb file.
Why is this appearing and should I have done something or do something to make it a Access 2003 format?
2. I am at the point of deplying the db to a small group of users (about 5). Some of them may have Access 2000 or Access 2002. Should I be doing something in particular to make sure things work in their machines. Any pointers to what may be problems or what I should do will be much appreciated.
