I am having some major problems so i thought i would ask you guys out there for some help because i am starting to bang my head against a brick wall.
I have a simple database, well i have 3 but the problem is only occuring on 1. each of these databases sit in a shared folder on the company network. I am trying to allow multiple users access this database but every time a second user tries to open the database they are unable to get access and receive this message
The table 'MSysAccessObjects' is already open exclusively by another user
However i have set the default open mode to be shared.
can anyone help as i really need this database to open in shared mode.
Has anyone deployed or is anyone using an access database in a shared drive environment over a network? If so, how is the databases performance and what kind of problems/headaches do you encounter in this environment? Thanks.
Hi! I have constructed a database in Aceess 2002 that four persons or more are going to work with. The users have there own computers in the same network. And they are going to work in the database at the same time the database is placed on a shared drive in the network. They must have the possibility to work in the same bookingformular. Is there something that I have to think about so that everything works allright? I mean in the multiuser environment. I had a lot of problems when rhe same people worked with an Access 97 database, But I hope that Access 2002 is better for multiusers. Is that correct?
hi, am trying to create an application for a company that has a small call-center (strength 20). the db is in the central server and each caller sits with frontend on their computer. the central DB is shared on the network which these 20 PCs are accessing.
The frontend: 1 Form only which is based on a query that displays records. Form Lock property: Edited Records Query Property: Edited Records
As the telecaller starts calling the customer looking at the records, they are not able to edit certain records as the respective record is locked by MS-Access when am sure that no other telecaller has opened the particular record.
This is my first post but I am reading this for a while now and I learned a lot from this site. Now, I have a problem which I cannot solve and I hope that you can help me with some advise.
I designed database for production proces calculation and for warehouse management. I have BE and Fe which are on server and every user has the copy of FE for himself. FE is also on server. Maximum number of concurent users is 3. The problem is that sometimes I get wrong calculations.
For example, when someone click the button for finishing the production process, calculation of production cost goes wrong. But, that is not happening everytime. Let's say one of the 10 calculations goes wrong. I tested aplication localy on my computer and everything is working normaly. I also tested the database in network enviroment (in my house, BE on one and FE on second computer) and everything is also working good.
I have to mention that this factory is rather old and we are constantly experiencing power loss or voltage disruptions. And also I have to mention that network cables are not installed profesionaly. We bought several aditional UPS devices to secure the network from voltage disruptions and now I will test the database again. But, any additional help would be appriciated.
The strange thing is that I never get any kind of error message. Everything seems to work good, but when I look at the numbers I can see that some of the calculations are wrong.
And just one more thing. In my database I have some procedures which are based on several queries which are executed one after another.
In some places I have up to 7 queries which are executed one after another one (first query deletes the data from table, second one makes the initial calculation, thirdone updates the warehouse data, fourth is calculating the new price, etc.) Maybe this is the problem?
I have split my db and distributed the FE to client pcs while BE is on the network. To demonstrate it i have 2 users , userA who has read/write rights on the shared folder where BE is while userB only has read rights on the shared BE folder. When userA opens the FE he can get in(writing userinfo in the table on the OnLoad event) but when userB gets in the FE opens fine EXCEPT he gets the error that there was an error on the OnLoad event, which i am fine with because userB doesnt have right access to the db yet. But now if the FE is closed by both users and this time when userB logs(read rights only) in before userA(read/write rights) he gets in with no error on the onLoad event but now if userA logs in he is shown the same error on the onLoad event!!! i am totally lost as to what i have missed, can someome help? this is my code on the onLoad event in the FE:
Private Sub Form_Load() On Error GoTo formload_errhandler Me.InsideHeight = 5000 Me.InsideWidth = 10000 DoCmd.Maximize Me.picBox.Height = Me.InsideHeight 'authenticate the logged user Dim userName As String userName = Environ("Username")
'check to see if username is in the SECURITY table Dim objRS As ADODB.Recordset Set objRS = New ADODB.Recordset
With objRS .CursorLocation = adUseClient .CursorType = adOpenKeyset .Open "SELECT * FROM USER_SECURITY WHERE userID='" & userName & "'", CurrentProject.Connection .ActiveConnection = Nothing End With
If objRS.EOF Then MsgBox (userName & ", access denied") userAuthenticated = False DoCmd.Quit Else userAuthenticated = True End If
'at this point userAuthenticated is true 'log the user in USER_LOG table updating userID,dateEntered fields Dim objCommand As ADODB.Command Set objCommand = New ADODB.Command Dim strSQL As String
Dear All, My company have an application that is using Microsoft Access for the database. The Application created by VB.
Because of server hardware failure, I have to reinstall the server (OS Windows XP) dan also the Microsoft Access. Now my application cannot run in multiuser anymore after reinstall the server. My applcation still can run in client computer but cannot run simultaneously in several client computer, because if one client computer has access the database in server, the other client computer cannot access the database, raising error inform that the database already open by other user. what should I do to solve this problem ?
I have a form in a database that is just a look up form (you cannot add or delete records). How can I prevent this (see below or attachment) from happening?
************************************************** ******* 'FormName' has been changed since the last time you opened it, either by another user or because another instance of it was opened on your own machine.
Do you want to replace the changes that you or another user made?
*To save your most recent changes and discard the user's changes or your previous changes, click Yes. *To save this version of the object with another name, click No. ************************************************** *******
What's the best way to handle multiusers and forms? The database is split but sending the front end to all users is not an option. I've tried different settings thru the Record Lock...Locked fields...Allow Edits/Additions/Deletions...and we still get this message. I've tried adding 'DoCmd.RunCommand acCmdSave' to a timer. It doesn't help. I am at a total loss...does anyone have any ideas?
I not a big time DB person so please be gentle. I am a computer technician at a school district and need some help. We use a program called Aeries made by Eagle Software for out attendance and grading. It uses an interface that runs through Microsoft Access. There are two version of this software. One is the SQL version and the other just uses an Access DB on a server. We have the Access DB version running Access 2003. It was explained and accepted in the beginning that we didn’t really need the SQL version because of our district size which is some where around 1500 students. Our district consists of 6 school sites that are all connected with a fiber optic backbone running at 200mb with a minimum of 100mb to each desktop. We have a DB for each site running on 1 very beefy server in a central location. I’ve run my problem by the software maker and don’t feel like I’m getting much help. The problem I am having is slowness during login. When the first user of the day attempts to login the program is fast, about 10 seconds from “ENTER” to the main menu. As soon as that 1st user clicks one of the menu buttons anyone else who attempts to login to that database after that experiences at least 30 seconds from “ENTER” to the main menu. I’ve watched what files are accessed and when. I see that when the 1st user logs in, the systemxp.mdw file is accessed and a systemxp.ldb file is created. Then when the user clicks a button on the main menu, the sch05xxx.mdb is accessed and a sch05xxx.ldb file is created. The sch05xxx.mdb file is the main database file for any particular site. The “xxx” would be the site number. As soon as that file is accessed or that lock file is created the user will experience the long login times and sometimes as long as 4 minutes. I don’t believe this is a hardware problem. During the same time that users are slow I have made a copy of one of the databases onto the same HDD on the same server and as long as I’m the 1st person to open it, it will fly. The 2nd person is slow just like the rest. I also don’t think it’s a permission issue, at least not in the domain. I’ve run all these test logged in as myself and have Domain Admin rights to everything. I believe this is a “split database” with the tables on the server and the forms, and queries on the users computer. I read an article here, http://www.microsoft.com/office/previous/xp/columns/column05.asp called “Why is Access 2000 slow for more than one user?” Has anyone else had this problem or have a solution? If I’ve missed something and you need more info please let me know.Thank you for your time and I appreciate any responsesJohn
We are trying to cut down the # of spreadsheets we have and took a purchase tracking spreadsheet and turned it into access db (2010).
We have 3 sites, and users across network would be 1-2 at max might be in db at same time either recording a purchase, or updating a record on received items.
Can this cause corruption? Is there a way to set users up so it won't?
I know in older versions of Access there were shares that could be set up.
We recently put together a database for a call center. The file is located on a public drive, and all users seem to be able to access the file (at the same time) and input new information.
On one particular form, I've found an interesting problem: I've placed a button at the bottom of the form, which will go to a new record when clicked. The command to go to a new record is clearly in the OnClick event, however users in the call center have to click twice in order to execute the code. I don't have to.
We're using the same form, in the same file, opened with the same version of Access.
I've always setup Front Ends and Back Ends so that a copy of the Front End is distributed to each Desktop.
I've now joined a new company (been here 6 months now) and the way things are done here is that one copy of the FE sits on a share and users open it from that location. This file contains no local tables and all data is connected to either Access or Oracle databases using ADO. The FE has built been utilizing User Defined Types to read all data in to memory.
I have a multiuser split db with this code on a listbox:
Code: Private Sub lstsearch_DblClick(Cancel As Integer)
' The following is the variable definition for the error handler On Error GoTo lstsearch_DblClick_Error Dim ErrorForm As String Dim ErrorControl As String
[Code] ....
The error function sends me an e-mail listing the error, user, form and sub. Ocasionally some users get error 3049 when running this sub. It is generally one user out of about 10 or so and the db keeps working fine for everyone else. I have reviewed the back end several times and I cannot find any obvious corruption signs. I have compacted and repaired it several times with very small changes is size.
Hi guys, i read about this before but it did not work.
i am trying to hide the access environment but i couldnt. i read in this forum that if i have a bmp with then same name than the db, the picture would replace the access environment. I have done this but the only thing that i achieved was to see the picter before access env. comes and then it desapears and the access env. shows up.
I was wondering if anyone would be able to help me here.
I have a database created in Access .MDB. It operates allright on my machine. However, since this database is done for my client, i have a problem i need to ask for help.
My client doesn't have microsoft office software installed on their machine. So when i passed the database onto them, they somehow can only run it in the run-time environment. Don't ask, I'm not sure about this at all. Anyway, They came back to me saying that they have got a run-time error message in the middle of running the database.
On my end, it's hard for me to debug since it works fine here. I was wondering if anyone would be able to tell me how i could have this database run in the run-time environment as my clients do. This way, i could debug the problem.
Is it possible for me to run my access database in run-time environment? how do i do that?
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?
Hi, Im working on a database that has to be shared by 3 or 4 users. In on of the actions that the database performs, it has to delete records from a table first. When sharing the database, it always asks the users (using access viewer) whether 'they are sure that the want to delete the records'. Does this always happen? And why? How can I get rid of it? Would it matter if I change it from a table to a query?
I am currently using the SetValue function from within a macro to set the value of one text box to the value of another. It works fine under full version but when I use it under Runtime which is where the final application will be run from, it brings up the Halt box and will not continue the macro. Does anyone know what can/cannot be done within Runtime. Is it just the same as A full version but without Design functions or are some other functions removed. I am painstakingly having to go through all the vba code that I wrote in full version and I am having to change so many things in order for it to work with Runtime. This is a real pain the backside! Any thoughts would be huuuugely appreciated.
Can anyone give me some ammo to tell me boss what a safe number of users of an access database is. It is a well built database that runs quickly and effiecently but I need to know at what point this will be put at risk. 100 users? 200+? I am running the database a FE/BE with the client sitting on each users pc and the BE sitting on a server. The network is 10/100.
I am using MS Access 2000 in a Windows Terminal Server 2003 Environment and the performance is incredibly slower than running the same job on a Stand Alone CPU with Access 2003.
Any idea? Access 2000 is running slower on a TServer? May the Access version difference explain the difference?
I've gotten to a point with my database where I have split it into front and back ends, and then made a copy so that I have a test version and a live version. I have users in live who've started keying data, and I'm working on forms and tables in test that I then copy to live as they are completed. Up to now, I've been just copying the individual item in test, and then pasting it over the version that exists in live (example: I made some changes to a form in test, copied that form, and then pasted over the version of the form that was in live).
Where it gets tricky is that I am also in the process of designing and insurance underwriting feature that's going to be a part of this application. I've set up all the tables in test, and now that I'm working on setting up the relationships, I'm wondering how I'm supposed to copy the relationship setup into live. Am I supposed to be copying the entire front-end from test when I have changes, and replacing the existing "live" front end with it? And if I do that, will I have to edit it every time to keep the new live front end from sending data keyed into it to my test version (had that happen when I initially split it)?
