I was wondering if there was a way to view mdb file without the navigation pane and ribbon (for Access 2007). I know I've used an access database that someone else made and it was done in a kind of "user-only" style interface where all you saw was the forms and reports in a dialog box style. This kept the user from seeing any of the tables and queries and all the "under the hood" types of things.
I have a multi user database in Access 2000 that is on a server. The individual users have shortcuts pointing towards the server instance. One user and one user only when opening the shortcut gets the error "you do not have exclusive rights to the database" .
All other users can enter the database with no error box. I have checked the advanced setting under options and they are correct. Ironically if you go to start and open access then navigate to the database shortcut. It opens with no error.
I would like your opinion on this; I have a ms access database that will be used in a multi-user environment, across different Teams. Data will be loaded from text files several times a day in a MS Access table, users will retrieve the data from the tables and displayed in a form. Their job will be to add comments and select drop down boxes for actions they have taken. Since the data is downloaded in the tables and retrieved from the user instead of the user keying in the data from scratch I would like to know how to best design this. I’m thinking of having a query run to display the data in the user form but is there a way that I can have the data refreshed every so often so that users can be presented with the new records that are being downloaded. What best practice should I use to avoid conflicts like example splitting the database or using record locking options
Hello Everyone! I have a project that is driving me crazy!! :mad: I have a form on a database that retrieves data from a query; this database is in a multi-user environment. What I am trying to accomplish is to allow the form to bring up the next available record that has not/or is NOT being worked on yet. The form I built does a re-query every time the user goes to the next record and looks for anything that has not been worked on yet. It does this by looking at the timestamp the user has placed once completed the record on the form. I also placed my record locking option to Edited Record. However when the users sign on simultaneously they still get the same item on their screen. Is there a way to create some sort of locking mechanism that would allow the form to display to the user the next available record that has not been or is not being worked on by a user at this time? Theoretically I am looking at something like this: Once a user opens the form and the record is displayed on the screen, lock the record and avoid any user from viewing or editing this record. All other users should be directed to the next available record, every time the user hits the next button move to the next available unlocked record and immediately lock it from viewing or editing from everyone else.
I appreciate any help you can provide me on this!!
I have a 2000/2003 format database used only for reporting.
It has linked tables to an SQL Server database.
It automatically opens a form with two buttons on it (no data) and hides the database window and the regular menu, replacing it with my own toolbar.
The default open mode for the database is "Shared." The default record locking for the database is "No Locks" On the opening form, the record locking is set to "no locks."
Yesterday, no problem for two of us to share it.
However, when I open it on my computer (not to edit - to use. I simply open it - not in exclusive mode.), and then another person opens it, they get the message that says "the database has been placed in a state by "Admin" on machine (my machine) that is locked and will not be able to be opened." (not verbatim, but close.)
When the other person opens it first and then I try to open it, I get a message that I don't have exclusive access and will not be able to save changes. I have to hit okay about 6 times, but then it opens.
Some users at off-site locations are having problems sharing - some are not.
i was told i could use statements like GRANT SELECT ON Accounts TO Web_User, only i dont know WHERE to write the statement and how to write it so it grants read only permission to all web users.......im using Microsoft Access 2013.
I am currently attempting to setup a database that will be used by many people. I have the database setup and it is split into a backend (tables and data) and a front end ( forms, queries, etc) which the users will download and use off their own machines. I'm attempting to house the backend on our webserver.
The backend is on our webserver and I'm attempting to link the tables from the front end to this location. I typed in the webaddress into the open menu after selecting the Get External Data --> Link Tables menu item. I am sure that this web address is correct because I copied from my browser (from which I was able to download the database from). After I put in the web address into the open box, I get an error about not a valid file name. Is there something I'm not thinking about? What could be my problem? Is it permissions maybe? Does there need to be something special setup with the backend or my webserver? Any ideas as to do with the problem would be greatly appreciated.
Another baffling problem - there are far more traps for new players than I ever imagined. Any suggestions gratefully received.
I have a fe/be split database with multiple users on a network. All users have the same front end on their PCs and are either running Access 2000 or 2003.
Problem 1:
Some users cannot open the database at all, getting the error message "Could not open xxxxx.mdb - File already in use."
Problem 2:
Some users can open the database but get a message in the status bar saying "Recordset not updateable."
Other users, running either Access 2000 or 2003 have been able to use the database without difficulty. The number of users is in single figures and it is unlikely that more than 4 people have attempted to log on simultaneously.
The database default open mode is set to "shared", the default record locking is set to "No locks" and the "Open database using record-level locking box is checked".
I have been having difficulties setting the security for the database (see other postings on this site) and so it is currently unsecured with no password set for the admin user. Users are joined to their default system Workgroup Information Files.
My guess is that there is a setting on the Access installation of the user's PC that needs to be changed but this is only a guess - anybody any idea what I should try next?
My database is on a shared server and many people are able to access the database at any time. What would be the best method to create a way for me to make design changes, etc. without having to make sure everyone is out of the file to allow me to open exclusively?
Hello, I am in the process of creating my database and I was looking for some guidance. My goal is to manage and track clients attending our program and ultimately being able to print and individual report with that information. Example: john doe on 12/28 attended 3 groups X,Y and Z. I have created two tables one with the client's ID, name and starting date. The second with the groups offered, the instructors and days and times of the groups. The third I believe should be a dated table that would have groups and all the people who attended that day. This is where I am getting confused. I am not sure how to proceed. Any ideas or suggestions would be welcomed.
We have an old computer that is going to be used as a simple signin and out book for volunteers. We want to restrict people on that computer from doing anything else
I have designed the form, and it is nice and evil in that it doesn't allow you to close it (cancel = true in the forms unload event) or even quit access without killing the process manually with the old ctrl-alt-del (or ctrl-shift-esc) it starts on startup and I have disabled the windows key (using XP so I had to add a binary value to the registry manually)
The problem is they can still alt-tab out of there (despite a NoWinKeys registry key that was supposed to stop that), and they can still change the main access window's size and access the start menu.
The network and local profile is such that they can't do a whole lot if they do get past the form, but there should be a way to stop them from leaving... some sort of API that will regain the focus, then I could just check that the application had the focus every second, and pretty much render the computer un-usable
Okay, wonderful gurus! I'm getting ready to split a db and I'm seeking advice or counsel from you. I know how to do this, but want to make sure no one out there has some mystical secret to reveal. What do you think I need to know before I do it? Assume that I've done this before and am looking for little "good to knows".
One MAJOR question I have is concerning the security involvement. I am going to assign a workgroup (security settings) to the db, and I'm wondering how to make sure that both ends are usable with security after the split. I know this is confusing, but I know how smart you all are and I'm hoping you know what I mean.
I've read instructions for making a multi-user Access 2007 database. Summary is:
1) Split the database 2) Put back-end part of the split onto shared drive 3) Make copy of front-end of the split and give to each user of the database 4) Open Tools, Options, Advanced Tab. Set the default open mode to shared and the default record locking to edited record. While in options area, go to general tab and turn off compact on close and name autocorrect.
These instructions were posted by an Ms-Access MVP.My questions is about step 4. How do these settings get saved to the particular database that I am trying to make multi-user? None of these settings are in the Current Database Tab for Ms-Access 2007. Since they are in the general tab, does that mean all database I open with my copy of Ms-Access will take on these multi-user settings?
I've created a database and I now need to set up user accounts for access to it, so that I can restrict who has read only and who has write only permissions.
I've done this before and never had a problem! But this time, whenever I try and create a new account, the following message is displayed:
Cannot update. Database or object is read-only.
Can anyone help as to why I get this message and what I can do to stop it! Whilst it does this, I can't create any user accounts.
I don't have the database finished so I can't really comment on the structure. However, I know the database will be used by multiple people, very likely at the same time. I've heard it's a good idea to split the mdb into a frontend and a backend so I've already started that process. I have no idea how this would fit into a security scheme though. Do I have to set up user-level security on both ends? Without actually implementing it I kind of think it would be secure if the backend had a master password and the frontend had user-level access. What do you all think?
I have very nearly completed designing and making a database for stock control for my company, and am now a little concerned on how it is going to be implemented. It is going to be done over a network, with only a handful of users. The idea is to have every user log in but with each person having different permissions. i.e onl;y being able to access maybe one or two forms, but also having an administrator that can view every form. Now, i am aware of the security settings in the tools menu, would this be the appropriate way, or would i have to creat an empl;yee table and set permissions thropugh vb? This is the first database i have constructed and need a little help!
The second problem is that the database will be over a network. Would i have to put the backend in one place and then have the front end installed on all the pc s and just access the backend when i its needed? Forgive me if this sounds a bit stupid but as i have said this is new to me..
I use a database that someone else set up and is no longer here. To get access to the database you need to enter a user id and password. I have a new user who has been getting into the database using an established user's id and password.
I went into the file and found the table with the users, their id's and passwords listed, and added the new person to the table, but I still get an invalid user message when trying to access the database with the new user's information.
I went through the Access Help and tried a couple things it said for adding users to a password protected database, but either I didn't do it right, or the way to add a user is different from what I am getting from Access Help.
Lastly, this database is different in that if I would add a report, it only shows up on my computer when I access the database, the report doesn't show up on anyone else's. That is odd to me, but it is how it works.
We have added a new user, following the steps that we always follow, with no probs upto now.
He's showing in the list of users with membership of the correct groups.
However when trying to login with his username and password although it looks like it's accepting username and password as normal and database begins to open we then get the following error message
I have had this in another Access forum ... without a resolution. I am pulling out what little hair I have left, so hopefully someone can help me.
I have created a program using MS Access that a small business will use to enter service contracts and invoices. The program was created in Access 2000, but converted nicely to Access 2007 which resides on the 3 brand new Dell computers that the business bought.
I did some research and determined that since 3 people would possibly be using the database at once, I needed to split the database. I did so using the wizard contained in Access. One of the computers acts as the "server" and houses the back-end of the database (in a "Public" folder that is shared to anyone on the network ... with all rights). All three computers have the front-end (forms, queries, reports, etc.) The front-ends all point to the shared "Public" folder on the "server" computer.
In each of the computers, the program will open and work properly. The problem comes when trying to access any of the input forms (that get data from the back-end). Only 2 (and sometimes 1) of the computers will open the form at the same time. If 2 are currently open and I try to open the third, it will sit and crank away as if it cannot find the file. It will not open. If I close one of the other forms, the third will open immediately with no hesitation.
At first I thought it could be a network bandwidth problem, but all are running at 50 - 100 Mbs and shouldn't have a problem opening a simple database file. I can't find anywhere that says Access would limit the number of users to 2; everywhere I look says that a split database should allow up to 10 users at once.
Again, the program works fine ... I just can't get it to open by 3 concurrent users.
I created a database for multiple users, it seems only one user can be in database at a time. Is there a property that allows multiple users to simultaneously use database. My record locks property is no. Is there some other property that needs to be set ??
I want to develop my database and forms to fit a 1600 x 900 resolution screen and would like to know, whilst I am in the Developer mode of Access 2007, is there a key that I can press that will switch to display the database/forms so that I can see what the User will see?
I have an Assess 2007 database with a user table. This table holds database user names and user passwords an entry permission to the database. I also have a welcome form that activates when user enters the database using either of the user names and user password in the user table. Now, I would like to display the database user name (NOT THE SYSTEM USER NAME] on the welcome form of the user that enters the database.
I have developed an access database, and prepared its run time exe file. My question is how to develop the database so that the user can regularly backup the database?
I have a call log database that is used to log calls (Obviously), i have several users over a network and everything works great, but i have been asked to create an alert function that notifies the user when a new call is logged assigned to them by a different user, similar to outlook when a new email is received.
I was planning on having a timer even which checks for new calls every few mins or so and opens up a form to display the new calls which have not been dealt with i thought it was gonna be simple but i have come across a few problems.
1. verifying if a new call has been logged 2. displaying only new calls 3. only displaying alert once per new call
I have attached the database but have had to remove all information from the tables for security reasons.