General :: Cannot Share Back End Database Under Multi User Environment
Apr 2, 2015
I have a Access data base (2007) which i splitted and store the back end database in a file server where all users have full control and the individual copies of front end put in the users computers. Unfortunately when one user is using the programme, others can not use. Following error msg appears. Both back end and front end are running under shared mode ( not exclusive ).
"Could not use xxxxxx_Be.accdb; file already in use."
I need to allow my MDB to have 15 users accessing at the same time. They will be updating different parts of the same table using different forms. The system will also do an automatic update from another system in 15 mins interval.
Is it possible? If so, how do I configure my access database?
I'm in the process of rolling out a new database that will require some data entry from approximately 35 users.
I have been told that database corruption WILL (not might) occur if more than one user is in the database at a time, which I find hard to believe. I was told that if multiple users who have different permissions levels are in the DB at the same time, this will cause corruption.
Has anyone heard anything like this?
Also, there will only be one or two forms that my users will be using for data entry. The rest is report running. If I set the value Record Locks on the form to EDITED RECORD, will this prevent corruption?
Any input you could provide is very much appreciated. I haven't been able to find any info specific to this issue.
I have multiple users entering data on bound forms. I have three required fields, all in the first 3 fields of the form. My question is, can I program something to where Access will update the record, after the 3rd required field, so that other users are not having to wait to enter there new record?
I have multiple users entering data on bound forms. I have three required fields, all in the first 3 fields of the form. My question is, can I program something to where Access will update the record, after the 3rd required field, so that other users are not having to wait to enter there new record?
I have a problem in multi user enviroment, with finding and locking a record in database.When one user finds, blocks and edit record ... another user in the same time can find the same record and overwrite it (User and Status values). It is just like he didn't see the changes making by another user.Each user have a copy of the front-end, back-end is on the shared disk.Here is the code to find new record:
Code: ... Set rs = db.OpenRecordset("tblTable1", dbOpenDynaset) rs.FindFirst "[Status]='New' And [User] Is Null" ws.BeginTrans rs.LockEdits = True rs.Edit rs![User] = username rs![Status] = "Assigned" rs.Update ws.CommitTrans rs.Close
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 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 ??
The front end has been saved in a accde format and distributed to 20+ users. They have all saved this onto there computers and this is used as an application.The users complete a form on a weekly basis on the application and then save. This then saves into the back end.For some reason I have noticed that a few users submission randomly do not save. For the life of me I cannot understand why.All users have saved them into the back end in the past but every now and then submission for users do not save.
I am developing a database for a company with about 10 users of the DB each using the DB on their own PC/Mac.
The workplace does not have a network. All work is done and stored on their own computers. They do not have a server either.
They do have a BT Business Hub providing broadband both wired and wirelessly.
The database is built using Access 2010.
I need to set up user groups/permissions on the database so certain staff can only see certain forms/tables etc...
What are my options here?
There is money available to buy a server or whatever. But ideally if there is another way of storing it and doing it, then I would like to give that a try.
I was reading somewhere you can use the Hub to create a small network, is this possible? And if so, whats the set up process for this?
I currently have the following setup for my database which is working as desired when only being used by one user at a time:
Front end: Access 2010 database in Citrix Back end: SharePoint List
The problem is that only one user can open the Access Database at a time since this action locks the database for other potential users. The locking occurs due to this link to the back end SharePoint list.
allow multiple users to update the SharePoint list through the access database at the same time?
I am developing a small database for use in a multi-user environment: I have split the tables off and am testing with two copies of the front-end on different machines. All seems to work well except on one form.
On this form, the value of a bound control (exposed as a number of radio buttons) is used to make related controls on the form visible or invisible. I use the AfterUpdate event to trigger appropriate VBA code to accomplish this; it works well.
However if two users have the same form open at the same record (unlikely, but not impossible), and User A changes the value of the control via the radio buttons, Access will eventually propagate the change to User B's copy of the form but the AfterUpdate event will not be triggered and the form becomes inconsistent. I understand that events are only triggered when a user makes a change to a control; how can I be alerted when Access makes a change?
I want to consider ways of sharing an Access database within our company. This could be web-based via our intranet or done some other way.
I understand that Microsoft's preferred way of sharing via an Intranet is to use SharePoint. However, as we don't use SharePoint (we use Atlassian Confluence) the cost of that route would be prohibitive.
Any methods of sharing an Access database across, say, 20 people? Simultaneous read/write access would be required but in reality the usage will be low, so performance is not really an issue. I would like to consider web-based or other methods.
I have chosen Access 2013 simply because we use Office Professional 2013 and Access will be familiar to some developers. We could use a different product. But I would certainly prefer a tool that supports RAD design of forms.
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 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.
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?
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 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 have build a single user application in access 2010. now i want to build multi user application and want to deliver to end user.how can i make my all vba code safe from end users.
We are encountering severe performance problems when running our access database on our Network.
Symptom:
Huge drop off in performance when 2nd and subsequent users refresh links to chosen back end database. If the database is opened by another users front end database.
Takes up to 10 minutes to refresh the links to 120 tables in Back-end MDB database.
The system is designed as a split front and backend Access database. The back-end Data MDB database is located on a Windows 2000 server.
The first time a user logs on they are required to locate and Re- Link the tables from the back-end database which holds data for the current year. If they wish to work on another year they re-link the tables from the relevant back end database.
When running locally the Front end takes between 5 and 10 seconds to refresh ALL the links to around 130 tables.
When the back end is on a network drive the process takes about twice as long. But is still quick.
If another user has the file open via their own (locally held) front end, then the refresh link process takes between 5 and 10 seconds PER TABLE !!
This means that that it takes up to 10 minutes to complete the re-link. Same behaviour if using Linked table Manager or refresh links using code
As soon as second user logs out of database the refresh link process speeds up.
The behaviour has been observed on a variety of servers and customer networks.
General data access is also much slower after 2nd user - but just about bearable. Data files are small – few records – occupy 7mb on disk.
Development Platforms – Windows XP / 200 clients, Windows 2000 Server hosts the back end database.
Front end is Access XP (MDB or MDE File) with al the latest service packs and security updates installed.
We have experienced this problem with a number of different systems running in various environments. But this wasn’t a problem with the old Access 1 database
HELP! Access should be able to support 10 – 20 users - we can barely run 2!
There are between 10 - 15 users at one time. It is a shared network, the front_end is on individual hardrives and the tables are located on the server. We just converted to Access 2003, our data file size is 47kb.
Users who are not active in the database get disk or network error message and have to close out. Is idle time a possible factor? Some users maybe entering information sporadically through out the day, but need to have the database open, they may need to refer to a member record upon receiving a phone call.
Bottom line I'm in bit of a pickle, work has moved forward the migration of Office97/NT4 to Office2003/XP by 2 months (clever lot) and was hoping not have to cram for this question until at least 3-5 weeks.
I'm looking for pointers/suggestions because I now have to test in Access2003 Runtime on MONDAY!!!!
What it is, is:
I have a query which is a list of items that need to be worked out of 65,000. Of that 65,000, 20,000 end up in the query (Actually do need looking at after an Automated process) (it's adapting the query/process I think I need)
Query:
EntID - UniqueID for a household Applicant1 - Number lookup value for Applicant 1 Applicant2 - Number lookup value for Applicant 2 Qualifies - 1 = Yes, 2 = No, Null = Not worked.
That's basic building block of the Query which is Drives the main Form.
What I would like is a scenario similar to this:
Person A opens record 1
Person B opens record 2
Person C opens record 3
Person C finishes record 3
Person B finishes record 2
Person C opens record 4
Person B opens record 5 (he/she took a little break)
Now that's the way I would like it to work, but there will be other factors and this is where I'm all ears for anyone who is used to this type of system.
The problem I can't figure out is that the Main Form has several subforms, but none of the data is to be edited, it is there for visual purposes only. The users will be creating records via the Main Form through code, but not directly into any tables/queries with which I can use conventional record locking, that I can see.
My thoughts are that Person A calls up a record based on Min EntID and somehow locks it so the Person B looks for Min EntID Where not locked.
Please, please can someone point me in the direction of how to do it and more importantly the correct order of events? I have tried doing the Min EntID and locking the record, but while Person A is running the Min Query, Person B is running it also so they end up with the same record as B has the record on screen while A is locking it.
Also, In the real world Person B might open record 2 and think, nah I can't be bothered. I would like a proffessional opnion on whether C opens record 2 or should B be made to deal with it.
I think not given the huge time constrants landed square on my lap, I would get there with smaller questions, but I've spent the last 10hrs writing a Function, to get it ready for the testing lab, where the owner has changed the requirements 7 times and my head isn't working.
All or some help given will be GREATLY received. Any further information needed, just ask.
