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 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 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 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 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 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 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 hope this hasn't been addressed too many times before, I searched for 'corruption' but there were so many results that I could only parse the first few pages.
Anyway, I'm developing a C# app for personal use and I was planning on using some MS Access functionality, namely saving and loading data from MDB files. Unfortunately, I've heard a lot of scary stuff regarding Access's tendency to corrupt MDB files. This is really bad news, as I really can't afford to lose any data - information is fed into the application daily, even hourly, and the data isn't stored anywhere else.
I could - and will - add some code to back up MDB files on every access, but I'm still curious. Given the circumstances listed below, how likely is Access to corrupt a MDB from time to time ?
- I am the sole user of the database. It is never, ever, accessed by more than one user at the same time. There is no networking involved whatsoever. - The database contains only tables and maybe some forms. There are no constraints, stored queries, or any advanced features like that. The forms are never actually used by the program, they're just there to help in editing the database 'manually' should the need arise. - The tables contain only basic data, i.e. INTs, VARCHARs and DATETIMEs. No memos, images or any such stuff. - The database engine / system will not crash in the middle of a writing operation, or if it does, there will be a certified backup available. - There are only two possible operations that the program can perform on the database: either a bulk read on each table, or a complete replacement of all of the records in all tables. There are no selective insertions or deletions.
What I want to avoid most is a 'silent' corruption, i.e. Access reports having saved the table successfully, but it has actually corrupted some records. It's not a problem to keep a backup for the duration of a writing operation (to cover the case in which the engine crashes during writing), but if I need to keep it for anything longer than that, the situation becomes rather cumbersome.
I was wondering if there is any way of stopping people from seeing the tables that I have created and the relationships between said tables?
I want to restrict access so that users can only see the forms and access the reports that I've created but am not sure how to go about stopping people from seeing, never mind altering, the table names and structures. Can anyone help??
Hoping someone can help me here. I have a form which is maximised on startup which also has the min/max and close button disabled. What i'd like to do is also prevent the user from restoring the form to ie. click the restore button which then makes the form smaller as i'd like the form to permanently remain maximised.
I'm not sure if this is possible, but if not is there a way to size the form to fit the height and width of the screen as if it was maximised regardless of the screen resolution the user is using.
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 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 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.
I maintain a database that is used by several people in my office. Only about 4 different people actually use the database but I would like the database to have multi-user support. As of right now the tables, forms, modules, etc. are all in a single mdb file. Can someone recommend a method for making this database accessible to several users at once? My main concerns are accuracy (changes commiting in the proper order) and low chance of corruption.
Hey everyone, I am in desperate need of your help. I have a split database that I am trying to enable multi users access to the database. I created a folder on the share drive with the front end and a folder on share (BEN) with the backend. I have changed the settings via options, advanced options, and checked that shared box however it will still not allow everyone into the database at the same time. Is there something that I am missing? Should I then right click and copy and paste the front end to local PC since the tables are split and still on the share drive???? I plan on using security in the future will this cause a problem???Thanks
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
:Hi, At the moment I'm writing a production database for work, which include parts in/out, production planning, kitting lists and other forms. What I'm after is a way that when the database opens it asks for a password and depending what it is, is what you can do. Administrator can do all, Stores can only enter parts and scheduler can only enter planning and so on.
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!!
Hi everyone, can anybody help me on this. I have two PCs connected and i am trying to execute an Access file from the client PC. This appears to be possible but the problem is that i cant save any new record and Active X or OLE seems to be the problem according to the message box appeared when i execute a form. The file works normally when executed from the server. Any ideas? It appears that the problem comes when Vba Code is executed for example i can save records from the tables but not from the forms where VBA code is attached
Hi all, question about using a table for temporary storage. When a user clicks a button after selecting critiera, a form is displayed with fields bound to a TempTable. On this form is a subform which pulls 3 peices of data from a table called QuestionsTable. As a user clicks through the subform, two fields are populated by the user and get stored in the QuestionsTable.
Once done, the user clicks a button and a SQL statement grabs the data from the main form (TempTable) and subform (QuestionsTable) and shoves it into the Archive table. A SQL statement then runs to delete the contents of the TempTable, and Delete the *modified* data in the QuestionsTable (by simply setting the 3 fields which will change to " " or Null).
Now my problem. If two users are in the same form and one clicks save, the SQL statements eraase everything... so the 2nd user will be mid process and their data will poof.
I want to assign a Session ID each time the main form is loaded. This is set via AutoNum in the TempTable. My question is, how can I copy 3 fields (Question, Comment, Result) from the QuestionsTable and insert them into the TempTable, then have the subform load the 3 fields from the temptable (so in essence, everything is loaded from TempTable).
Did that make sense? Sorry if it didn't, I'm reaching my deadline on this and have a bad cold
I have a form "log_file" that I am going to be placing a nework. All I have done is create a new DB, create a table, and create a form. Now I want to make it so users open up the DB file and only see the form and cannot access/edit the table. Basically, It is okay if they go back and forth through the records and change those, but I don't want them to be able to edit the form either.
I'm just not sure where to go from here. If there is more info I should provide please let me know.
