I am new to the Access database building. I am trying to create a Student database for contact information, etc. I have a main table which stores all the users' data. When the student opens the database, I would like to identify the user. They should be able to view everyone's information, but only edit their own. How can i make this happen?
Also, if that is easy enough, I would like to identify when a staff member logs on. This way they can have special permissions to access a schedule searching feature, to look at all the students schedules.
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)
Installed Access 2003 recently and could swear that on a form in design view, sizing a control button for example, by holding down shift key, worked as I expected; it sized up or down by 1/4th of a grid line.
Today, I hold down shift and size a control, and it sizes up or down by one full grid line. Can't find anything in Options that I might have changed, nor in the Format menu.
I'm new to my job and ms access and not very savvy in the latter. There are fixes for my problem on the internet, but I really don't understand them.
I'm used to dd-mm-yyyy format and it's tough for me to think in mm-dd-yyyy in, for example, MS outlook. If I change my regional settings, of course, outlook and access follow suit. The access database is shared and we print out records as cover sheets for our files. Thus, it's not an option to have me on dd-mm and others on mm-dd. Is there a way for me to enter mm-dd in when using the database but have dd-mm standard for every other aspect?
If you can help, which I would appreciate immensely, please pretend that I don't know what I'm doing.
I designed a query, opened it and printed it. But the margins were too wide and I needed it to print in landscape also. So I changed the settings and it worked fine, but I can't get it to save the settings. Is it possible to save the printer settings for printing a query, both the margin and the landscape settings. If so, please tell me how. Thanks.
Hi. I have had a server change and db was moved and I need to change the IP etc. Is there a easy way to do this? I have searched through this forum in vain. :( Kind Regards Marie
This is getting into some stratospheric territory for me.
I am trying to change the visibility property of a label and corresponding text box, based on the contents of a different combo box. cboHow is a combo box that uses a value list as its row source, since the content of the list won't change. There are three fields that I need when the content of cboHow = "FIS". Otherwise I don't need them and I don't want to see them. My code is below:
Private Sub txtFISDepartmentNumber_BeforeUpdate(Cancel As Integer) If cboHow <> "FIS" Then lblFISDepartmentNumber.Visible = False txtFISDepartmentNumber.Visible = False Else: lblFISDepartmentNumber.Visible = True txtFISDepartmentNumber.Visible = True End Sub
At the moment there is no error code, but the label and text field don't respond by becoming visible/invisible when the contents of cboHow changes. Do I put this code with the txtFISDepartmentNumber or in cboHow? and do I use BeforeUpdate or AfterUpdate? Should I have a separate If..Then..Else for the label and the text box?
I have been playing around with this for several hours now and seem to be going in circles.
I have a report that prints labels. Every few times of opening the report, the page setup settings revert back to default i.e. 1" margins, 1 column etc. how can i assure that these settings remain unchanged?? thanks!
I am working in a constantly changing db. The new regime is trying to calculate an inmates remaining time to work on the freeway trash crew if: 1) They show up for work and 2) have no FTA's. This form field is unbound. I currently have a query that calculates the days if they did show up for work or they had served their time. Since there are over 2500 inmates in the program, and the man power to update that many files daily isn't an option, I think it would make better since if we documented the ones that didn't show up but at the same time credit the ones that did...can this be done? If so, any suggestions. Thanks in advance.
Why does one have to enable all macros in the trust center in order for VBA to run? I'm making front end applications with Access and having to allow ALL macros to make them user friendly makes a huge hole in general security. I don't use any macros - it's all done by VBA.
Users are on a plethora of different platforms so changing reg keys is out of the question. Is there some way of self sign an Access accde? Is there some safe GENERAL approach (trusted sites is not good either) to allowing VBA from my applications ONLY?
I'm looking for a work around for getting the bound column setting for a combo box to work. I created a simple table with 2 fields that i have a combo box pointed to. My settings for the combo box are
Column count 2 Bound column 2
The first field is "Description" The 2nd field is "ID"
I cannot figure out how to have column 2 to be the value that is left in the combo box once I have made my selection.
Under Current Database, I have "Overlapping Windows" checked. When I open a table, it opens to pretty wide. Then I resize it so that it takes up less space. After resizing, whether I click Save or not, after closing, then reopening the same table, it opens back to its original size (very wide), instead of opening at the smaller size that I resized the table to.
Is it possible to resize a table, and get it to open at that size next time you open that particular table?
I have a huge problem!!!! Access seems to be picking up settings from somewhere which means that the Short date = mm/dd/yyyy and not dd/mm/yyy as set in the regional Settings!
First, thanks to all that have helped me with out even knowing it! This forum is a lifesaver.
Problem: I have a control button that, through macro commands that seem to be working, changes a field value from locked=no to locked=yes. This macro control also changes the enabled setting to = false.
When I save and exit the form, upon reopening, the above cell value is not saved. Is there a simple fix for a simple-minded person?
I am using this [URL] .... in our project but have made a minor change so it logs people out rather than close Access completely. It works beautifully but I want to take it a step further.
Instead of hardcoding the times in these two values
I'd like to give users the options to set these themselves as not everyone will be the same. I am thinking I would have to check for who is currently using the database, this is stored in a hidden form in the following field.
[Forms]![frmwhoson]![whoson]
This username matches the users First Name in table Employees and in this table I have two fields to store these values
logmeoutafter showlogoutmessagefor
So passing these values for the current user rather than having the logout times hardcoded.
But they do not work, there are still messages when deleting a record from an endless form by pressing "delete". I don't want to add a button. Docmd. Setwarning false in every form!
Thought I best ask this question BEFORE I run into trouble.
If I were to set my database to hide the database window and all menus on startup so that users can only do what I want them to do and not edit anything. How do I go about reversing this if I needed to edit something as I would not be able to see any of the regular menus?
It would be good if the solution involved some sort of admin password rather than a sneaky short cut that a user may accidently stumble across.
