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 responses
John
I'm having trouble with access. Basically it has been very slow to load (over 30 seconds when not opening a database) and when opening a database it just crashes.
Has anyone any idea what could cause this as it worked fine before ?
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?
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.
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.
Hi everybody, I have an access database which is around 40 MB after compacting it and I feel that it is slow especially when I open cross table form. Is there any way to speedup the databse. Note: my databse is on the share drive in my work.
I have developed a DB for work and it has grown, it is about 60Meg, all of a sudden when I am opening Design View in Reports, or queries it started running really slow.
I always Compact on Close I have Split the DB.
Still no Joy, I have a brand new Dell PC so nothing wrong there.
What is happening? it is a nightmare to get anything done.
I've been searching for an answer for a long time, but i have a database with approx 100 forms, 100 tables (most linked to SQL Server) only a small proportion are front end tables, 50 or so queries, 20 or so modules.
Anyway the problem is, is that the database is slow, to open and to develop in, i have a decent system to develop on with a 3GHz CPU and 1 GHz RAM, but i dont get this problem with any of the other access databases i deal with.
It's kind of a lagging effect, then once it has been written into memory it's quicker... but why would that be different between the systems, as most the systems i deal with are fairly similar in size and in complexity.
For example when loading the logon screen, which is a simple unbound form, it seems to lag, there is 1 combo box which has a front end table as its row source, like 6 records. Then a username and password text boxes which are not bound to anything. Why should this be lagging? After like 2/3 secs its then ok, once ive logged in and then go back to this logon screen its fine, so i think it has something to do with memory.
Anyone else had anything similar happen to them and did they do anything to minimise this lagging effect?
My acccess (.mde) application suddenly slowed down. I have increased the size for some fields in some Tables. Is it could be the reason for this? Is there any way i can get the speed back.
I have recently been doing a conversion for my boss for a access 2000 database (both front and backend) to a MSSQL backend.
I finished the conversion today (as quite a lot of the code / queries ran slow due to access running the queries locally rather than on the server). And tested it on my and my boss's machine with no problems so he gave the go ahead to update everybody to our new mssql 2000 backend with the modified frontend.
This is when the problems started; We had two different sets of forms for accessing one of our databases systems - the log system, one is the original dynaset based form, and the other is a newer set which uses snapshot views and preforms updates via queries. Nobody uses the old dyanset system apart from my boss and one of the administrative team as they have things on that window which they need to see. About 30 minutes into the release of the new database the system frooze up on my bosses computer and nobody could create a new log (the server was timing out). I assumed this had something to do with the old dynaset's creating locks on the table.
I offlined the database and kicked everybody out of the front end, turned it on again and tied again, this time banning everybody from the dynaset system. Within 10 minutes another computer frooze up, again with a timeout on the insert query. I discovered that after you had added a new log to the database it would timeout on all subquent additions (something it hadn't done during testing) . Further investigatiion showed it was the snapshot list window causing the error, so coded the add log window to close the list before preforming the insert query and then reopen it afterwards. This allowed my machine to make multible additions without flaw. So I released a new client to everybody. 15 minutes later it was timing out again, but this time there you could not even make one new record.
I checked for locks on the table though the server management table and couldn't find any for the Log table. I have restarted the SQL server box and with no avil. So I reverted our backend to the access mdb file and told people to use the old client.
I am at a complete lose to why this is happening, if anybody has had any expericences like this or knows the cause please tell me.
Some information on the database in question.
It was made as an access 2 database all intergrated into one file, then it was seperated into two files (frontend and backend). Upgraded to Access 97, then to 2000 before this final update to MSSQL 2000.
The log system has two main tables. The first is the log title / info table which links (one to many) to a log entry table. This problem only occurs on the main log table and does not appear to be reoccurring anywhere else within the database. The main log table has just under 18,000 rows in it.
I have access 2003 installed on two different machines. One machine was built 6 months ago with the best hardware available. The other was an older slow IBM.
For some reason, I am experiencing what appears to be some serious time delay (talking in the range of seconds, sometimes tens of seconds) when building a report that has a subreport in it on the fast machine. Yet when I load the exact same database on the slow machine, the report opens instantly.
I have an access database that runs fine on our current systems (mix of office 2002, 2003 and windows xp/2002.
However we have one new machine here running windows vista and office 2007 and the database runs super super slow. just about every operation takes 10 times plus to run!
I have looked at the sticky subject at the top of this forum and it's not the problem linked to here http://support.microsoft.com/kb/935366/ as this uis the only vista machine we have accessing the database. the same problem also occurs when running locally on my home machine (again vista and office 2007). From memory if is fine when running it through office 2003 on vista.
Anyone else have similar problems and find a solution?
Any ideas why a particular query would run very slow in access 2007 when it runs fine on 2003. This is running on a terminal services environment and the database connects to a ms sql 2000 server. I will try it outside terminal services when I can but I can't understand the problem. Im not talking about slightly slower its something like a factor of 100 or 200 slower (I had to limit the dataset just to get a return within a day).
The database was an access 2000 mdb for compatibility across computers but I have tried converting it with out any luck.
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?
Is Access slower at summing null records than SQL server? I have a query which takes less than 1second in SQL server but takes about 5-10 in Access but can't think why there is such a lag in processing speeds.
I have completed a database for a company with 60 000 clients and over 100 000 job records.
The database works at very resonable speeds on the Server computer, or the computer on which I installed the back end of the database.
Each of the other 3 computers on the wireless network, have a local copy of the Front End on their machine, and reference the Back End (BE) on the server computer.
Each of the Client computers have varing speeds when accessing the BE, some as slow as 10 minutes for a simple search, filter or just loading a form.
What can I do to improve performance across the network?
Do I need to install additional components on the other computers to improve the db performance?
I am using John Big Bootys Dynamic Search Form (built in Access 2003) as it totally met my search requirements, however when typing anything into the search box it is realy slow, taking several seconds for each letter to show in the box.
This has always been a problem now and again, however some of us have upgraded to Office 2010, (although still using the 2003 built Db as we won't move to a 2010 version Db untill March next year) and now the problem is even worse that ever. Everything else seems to work really well except for this search function, however it is the search function that is used more that anything else.
I recall reading somewhere (fairly recently) about a parameter or property in Access which is "On" by default and allows a form/query to identify when backend table field names or query arguments are changed and automatically looks for and "fixes" the renamed link. By leaving this switched ON, the database is slower than it could be. The db speed performance can be can be improved significantly by switching this 'feature' off. (i.e. Name of the property)
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.
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 ?
