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 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've got a database in Access 2007 that keeps track of client data for work. It's been working fine for about a month, and suddenly today other users can't change any information because the records are suddenly locked when accessed from their accounts.
I've already checked that they can't update forms, tables, nothing.
I've checked the database properties, it defaults to shared with no locks.
I've checked the properties of my forms - no locks.
I've double checked the permissions to the folder that the database is in - no restrictions.
I have designed a database which I intend to split for multi-users to access from one front end icon on a shared folder at work. I have designed a form bound to cmr record table and on it a subform to another table where cmrs activities will be saved. The form has buttons to and blank controls.
User can create a new activity entry by typing into the blank controls and pressing the save button which saves to the activity table. the edit button extracts a selected records details (selected on the subform) from the activity table and populates the blank field for a user to edit and then hit save to save changes. The delete button deletes a selected record from the activity table. I intend to have multi-users either accessing, viewing and a possibly editing the same customer at the same time. The simultaneous viewing is essential but the simultaneous editing, though not desired is inevitably going to occur.
What I would like to know is:
1. Can you lock an individual record in a table or does the whole table have to be locked. E.g If Colleague 1 is editing Cmr A's record in Table1 can he lock it so Colleague 2 can view and edit Cmr B's record in Table1
2.Can Colleague 1 access/read Cmr A's record in Table1 to retrieve details toe the form controls if Colleague 2 is viewing or editing Cmr A's record in Table1
3. If record lock is possible, how can I initiate it in my example code below.Edit activity record Code
Code: Private Sub Edit_A_Click() 'Get Data to text box control With Me.R_P_Data_P_Subfrm.Form Me.txtrID = !rID Me.txtrID.Tag = !rID Me.txtrefNo = !refNo Me.cmbrpc = !rPC
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 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 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 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.
I have a "client/server" split Access 2003 database with an Interface file containing all the code/forms/queries and some system tables and also a Data Backend file, with all the data tables and table structure.
This is being deployed to multiple sites, each getting their own version of the backend, so sites will not be using the same backend between them all, rather multiple users in each site will all share that site's backend file.
Since users will deploy in different network locations, etc. they will have to re-link all tables. Is there a meaningful/user-friendly way of doing that without relying on user's knowledge of "Linked Table manager", etc.?
I have a 2007 back-end db on a network share and around 15 regular users who access it through their own front-end db/interface. One user on Windows 7 is able to launch and use his front-end copy fine except when he goes to launch one form for data entry.
This form clocks and freezes the entire application. I sat with him and was able to determine that the issue is that the form_load code is never running. He clicks on the button to launch the form (done in vba) and the code never runs. If he opens the form in design view first then changes to form view, the code runs fine and there are no issues. This is his present work-around, but I had to give him an unlocked FE copy to pull it off (not ideal!).
I tried this with him on different PCs, with different front-end copies, and even in the back-end copy. Same result each time. None of the other users have this issue, and he can replicate this issue on different PCs. I'm at a loss for what might be causing this since it really seems so user-specific.
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.
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?
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.
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."
If I want to distribute a front end to connect with a MySQL back end ... do I need to set up the system DSN on each workstation that will be using the front end?
I've seen different log in forms and tips on multi-user use but can't seem to find info on the following...
We have 6 people at work and I'd like to assign which user updated a form or created a new record...this would be particularly useful on the sales part of the database to track who made a call to a particular customer...
I have read a lot about if multiple users want to share an MDB, they have to create BE and FE and split the database.
I understand having to do that if all those users want to write to the MDB simultaneously.
I have a situation where one person will do data entry (write access), and two other users will just want to view and perhaps just search the database (read).
If only one person is writing at any time, do I have to do all that splitting and FE/BE configuration?
I plan to create a multi-user application on access 2000. There would be more than 20 users simultaneously logging in the database. The database would be kept in Server with high config. The users would work on the database (server) from their workstations. Forms/Queries/Reports ... are in the workstation (client). The database may growup to 70 MB every 3 months. The application will run on the database for 3 months which will be replaced with a new one after that period. Is it a good plan to do so on Access 2000. Am worried about the network traffic. Will the users face it as a very slow application ???
Hi If I want several users to access a database from their network pc's, should I place the access database .mdb file on the server and set the Sharing properties, then install the access application on each of their stations.
They need to each be able to use the database when they need to and read or add data, reports etc.
