I have a DB which has been up and running with no problems for a couple of months.
A couple of users have recently had new machines installed. These are XP SP2 with Office 2000.
The Database FE is on the PC and the Backend is on the server.
When FE is first downloaded and opened it runs fine. The second time you go in the DB gets by the Splash screen but then crashes on the Title Menu. If you then recopy the FE to the machine it opens fine the first time then crashes again on the second attempt.
I have checked the references and all ok. I have full error trapping on the Splash screen and the Title Menu yet I just get the error "Access has encountered an error and needs to close..."
It runs fine on my machine which is XP SP2 with Office 2002. Has anyone any suggestions that I can check or repair this?
I've been experiencing a very frustrating problem recently.
One of my databases crahes randomly, and I'd like to know if some of you have tips to helps me.
The database is splited in front-end and back-end, both on the server. I know keeping the front-end on the client PC will improve performance, but due to a high number of users (about 60 to 80) and the need of doing frequent updates, installing the front-end on each machines is not an option for now.
Users are not all directly connected to the server. Those who are directly connecte4d to the server (in building A) have no problem. Those who don't (building B) have extensive lags on opening (about 30 seconds), and on about anything that calls an heavy query, most often leeding to a crash. Access display the message telling that the datbase needs to be repaired and restart.
I tryed several thing to improve my queries, like eleminating most of GROUP BY and UNIQUE clauses and avoiding the use of functions.
I have a lot of conditional formatting in the forms, but I don't think this is the problem, since it is executed on the local machine (as far as I know).
My theory is that the lags cause some call to the DB to timeout. I just dont know how to fix that. Is there an option to higher the timeout delay?
My other theory is that the problem is caused by dropped packets during the connection to the DB. I tryed downloading large files (100Mb to 250Mb) from the server several times and never had a problem. Although the connection is quite slow, the ping is very small, like below 10ms to 20ms. Is there better ways to test a network connection, if possible without installing software (limited rights on the machine)?
Would using Replicas be a solution? What are the pros and cons of it? I never used them and know very little about it. My idea would be of putting a back-end on both servers, but I guess the data would not be as live.
BTW, I am using Access 2002 (2000 file format) on an XP SP2 PC.
Thanks to all of you patient enough to read all of this! I Hope some of you have some awnsers, tips or tricks!
It seems to be quite simple really. Make a form for Orders and add a subform for Order items. Write some VB code to chage values on the Order form when an Order item is added or amended. Add a "Find" dropdown to the Order form to find particular Order numbers.
Run the form and add/amend orders and items. This will work OK. Move to the next or subsequent order using the "Next" button. Add/Amend again - no problem. Drop down the "Find" control, select an order and the correct order comes up on the form. Amend an item. As the code attempts to change a text box on the Order form Access crashes.
The same code (to add up the items, take off discount and add on tax) can be run after a "Find" by changing a "Discount %" text box on the Order form and this works OK. Perhaps the Order form needs to be in focus for the code to work but I cannot see why this should be so.
In fact you don't actually need the "Find" dropdown. Any code that moves to another Order record programatically will cause Access to crash when an item is added/edited subsequently.
Making it crash is simple but stopping it has cost me a couple of days of frustation. Has anybody any ideas?
My Access 2000 project crashed and the computer dutifully asked to report the error to Microsoft, so I let it run. I then looked at the subsequent screen and was surprised. Well - silly me, maybe I shouldn't have been.:mad:
This screen simply said that Access 2000 was in "extended support" and my "solution" was to upgrade to a newer version. This was a bit irritating since the purpose of reporting feedback is to provide an opportunity to fix program bugs. So why ask the user to provide an error report if that report will simply be ignored and only used for a sales pitch.
While Microsoft has every right to discontinue product development, I would hope that they would still try to fix bugs that cause a program to crash. I guess Microsoft's quality control department has been outsourced to the same company that Dilbert works for. Additionally, I find euphemisms, such as "extended support" for "You are out of any help options, tough luck" to be quite irritating. Why not directly admit that we are on our own.
Also I am still on a slow boil over over the last six years by the fact that help for DAO/ADO disappeared from Access 2000 help which was in Acess97 help and Microsoft never got around to making it available as an update.
So, my database appeared to be working OK yesterday however I occasionally saw an error in my "Update Event" script on one of my combo boxes. today, now when I try the combo box, I get a immediate crash.If im assuming its the same combo box, here is the code for that box:
Code:
Private Sub MCAcmb_AfterUpdate() Me.Model.RowSource = "SELECT DISTINCT [tbl].Record, [tbl].Model" & _ " FROM [tbl] WHERE Record = '" & Me.Recordcmb.Value & _ "' ORDER BY Model"
[code]...
I recently added a header...just tried it again and got the error:"The expression After Update you entered as the event property setting produced the following error:Object or class does not support the set of events."however I got it to work by entering VB, adding a space, removing it and then saving and entering the form view the form worked as normal. when i close and reload, i get the error again
I have a database that currently has security in place so that users input their own usernames and passwords to access the database. The users have recently been added to a windows 2000 server and I want to be able to use their windows 2000 server logon credentials to provide them with automatic access to the database. Is there anyone out there who knows how to set this up? It is a rather urgent request if you could get back to me either on this forum or via email
focking pissed off. i want to add an image to a some forms, the database is all working and that. but when i put a picture in in the design view and then go to view it the whole thing crashs. i nearly lost the whole data base from putting one on the home page, thank fock i had a back up and now ionly have to redo one form as the other one wont open anymore it will just crash every time i try to open it. i have no idea whats going on, i have other images that i put on it before, but i cant put any on now. anyone every encounted this and how do i over come it!
I am opening and closing a series of Excel 2000 Workbooks using Access 2000 VBA and want this sequence to be able to complete without any human intervention.
However, there are 2 instances when this stops and waits for a human option to be selected:
1. When the spreadsheet is password protected 2. When the spreadsheet has automatic links I get the message:
"The Workbook you opened contains automatic links to information in another workbook. Do you want to update this workbook with changes made to the other workbook?"
How can I code it so that in situation 1 it skips this file and in situation 2 it automatically defaults to do not update?
If I have a report in MS Access 2000 generated based on the criteria selected of a project with work order "9999" with the labor costs, materials costs and the Totals of each crew1, crew2,... and I would like to have those expenditures populated in corresponding cel in Excel for each crew, HOW would I do it?
To think it out loud, could I create a button on a form, so when I select the criteria for the work order, and when I click the button, it should refresh/update the Exel file with the new data...?? How do I write VBA code for that...?
I've got a bit of a problem with linking a text box to a ComboBox. I have an employee name in a field [EmployeeName] that sits in the Header of a Form. (This is so I can show multiple records for that employee without having their name repeated at each one). I also have the name of contact [ContactName] that sits in the Detail area of the form.Both names come from their own tables that have all their contact numbers and e-mail addresses in columns I have linked the name to text boxes [ContactPhone] & [EmployeePhone] with their relevant phone numbers in within the Detail area of the form.
The ContactPhone that has the ContactName within the Details part of the form works well with no problems by putting =[ContactName].Column(1) in the Control Source
However when I put =[EmployeeName].Column(1) in the relevant Control Source (and / or EmployeeEMail in a second text box), once I have saved the form in Design view and returned to Form view, Access crashes and shuts down!If I remove the wording from the control source Access doesn't crash.
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 two database applications and they are: - the (A) application is for administration use. - the (B) application is for normal users use.
the idea is that: I made the (A) application for administrators who have full control over the database objects (tables, forms, queries, and so on ...).
the (B) application I have created for normal users who will have only to use forms to insert some data and display data only.
but the two applications has a respective table called "vacation request" table. where I linked them, so the both administrators and users can share the data.
The real question is that: How can I prevent the users from seeing the database objects in their application. I used the database options which have helped me in hidding the database objectives when the users open the application, but unfortunately they managed to access to the database objects by pressing the special keys.
I would like to have an access to the (B) application when I want to make some modifications to the forms and then lock it from users where they only have to use the forms for requesting vacations and view the vacations.
I am working on a massave aplication that has been running in Access 2000, but recently several of the file sharing users have installed Access 2003 because of the limited availability of Access 2000. All the users are using the same file off the server.
The problem we are having is that when we reference a subform in the "[Forms]![FormName]![SubformName]![FeildName]" Access 2003 does not recognize it and returns an error. I have found that if I will modify it to "[Forms]![FormName]![SubformName].[Form]![FeildName]" it is recognized in both 2000 and 2003.
To try and change every instance of a subform reference will take forever and I am garuteed to overlook something. We reference subforms all over our program, missing any one of them would be a disaster. Before I went to the tedious task of looking through everything I just wanted to throw the situation out there and see if any of you had any great ideas on how to get it fixed efficiently. I would apreciate any ideas.
I upgraded a 2000 db to 2003 recently. When I ran the function below it gave me an error on the line in green. Any thoughts? Thanks. Const FIRSTROW = 13
Dim wsp As Workspace, dbv As DAO.Database, tblResolve As DAO.Recordset Dim tblVchs As DAO.Recordset, tblImpTmp As DAO.Recordset Dim ObjXLApp As New Excel.Application Dim FileToOpen As String, WhereCriteria As String, ImportTemp As String, tmpVch As String Dim TotalDupes As Integer, TotalGood As Integer, TotalRejects As Integer Dim TotalBlank As Integer, R As Integer, C As Integer Dim BadSheet As Boolean, ImpFail As Boolean Dim tmp, tmpType, tmpCtr, tmpRsn
If Forms![Import Block Vouchers]![Import Program] = "0" Then MsgBox ("You must select a Program to load.") ObjXLApp.Quit 'Exit from MS Excel Exit Function End If
I've created a database in access 2003 with the default file format being Access 2000. Everything works fine on my computer and many others, all of whom are running different versions of access (2000, 2002 & 2003).
I have not had any problems with this database until recently and in the last few weeks we have had 2 users, both of them being Access 2000 users who have had the same problem.
The problem they are having is that when they click on any of the switchboard items, the buttons depress an then come back up again when the cursor is moved away, but nothing else happens - no action, no error message - nothing!!! Its the same for all of the buttons on the switchboard.
Does anyone know what is causing this? I have another computer with Access 2000 on it and this works fine, as it does on several other computers runiing Access 2000, I just cannot understand why it is not working on these 2 particular machine.......
I have recently installed access 2003 w/access 97 installed both are on my hard drive. When I create a new db in access 2003 it saves it in an access 2000 format. Does any one know why it does this?
We have two computers in a work group. On computer1 I have the back-end and front-end database files in the shared folder and 2 users out of 4 can access the database no problem. When the other users try to access the database they receive the error message "Microsoft Access can't Find The Database 'C:Documents and SettingsAll UsersDocumentsdb.mdb' Make sure you entered the correct path and filename" On computer2 I have the front-end database files in the shared folder and pointing to the same back-end database on computer1. Again 2 users out of 4 can access the database no problem. When the other users try to access the database they receive the same error described above.
I expect that this is some sort of windows permissions issue? There are some clues to this fact .. The two users that can't access the database are limited accounts, but I tried making them administrators and this had no affect. Their shared documents folder does not have a hand underneath it?
Any help on this appreciated as it's really starting to annoy me now!
A few years ago I’ve made an access database on access 2000. The problem is that now I’ve installed the office 2003, and I can’t make the database work properly.
At first says that are missing those files: “tshoot.ocx”, “msioff9.ocx” and “msowc.dll”; so, I’ve copy them from another computer using office 2000 and now only complains about “msioff9.ocx” saying that my database contains a reference incomplete to it.
Is there no other way to convert my database do work properly with access 2003? What can I do?
The company I am consulting with uses Access 2000 and has no intentions of upgrading. I currently do not own Access on my laptop.
I was planning to purchase Access 2003 for my laptop but am concerned that files I create in 2003 might not be "editable" in 2000 even if I choose the 2000 format when creating new databases.
I'm just wondering if anyone has tried creating a file in 2003 (using the 2000 format - as I'm told you can choose what format you want to use) and then edited it in 2000. I want my client to be able to edit the files in 2000 once I've moved on. (I can get 2003 for about the same price as 2000 - so my preference would be to get 2003.) The other obvious reason for going for 2003 is that I could run into the reverse challenge if I own 2000 and my next client uses 2003. At that point, I'd be forced to upgrade to 2003.
My databases are not complex - but do include some customized macros.
I have recently installed access 2003 w/access 97 installed both are on my hard drive. When I create a new db in access 2003 it saves it in an access 2000 format. Does any one know why it does this?
Yesterday my database crashed. It is the 'DEV' version for my application - so all of the current fixes/changes are in there and I have forgotten to backup!
It crashes when ever I try to enter the VBA editor, or build code. This occurred after a minor problem running some code (I forget which code).
The same occurs when I try to get into the code builder in the repaired version access generates...I have also tried using compact & repair to get in - but still no joy.
Can anyone offer any advice workaround to get this up and running again?
I am managing a traffic database and have currently constructed a series of queries that list average vehicle speed and total volume in five-minute intervals over the course of several months. From each of these queries, I need to create a subquery that, for each time interval, will simply average all speed values and sum all volumes into one record. Fields are: Time, Avg Of Speed, Sum Of Volume.
I created the subquery like so: SELECT DISTINCTROW [Speed Weekday (2 SB)].Time, Avg([Speed Weekday (2 SB)].Speed) AS [Avg Of Speed], Sum([Speed Weekday (2 SB)].Volume) AS [Sum Of Volume] FROM [Speed Weekday (2 SB)] GROUP BY [Speed Weekday (2 SB)].Time;
When I attempt to switch to datasheet view though, Access locks up every time and I am forced to end the program through the task manager. The query I'm referencing [Speed Weekday (2 SB)] has only 4800 records thus far, so it isn't a ridiculous amount of data. Any advice as to what is going wrong? Thanks in advance for any help!
have a form that uses comb boxes. Now the combo box is Label "Tank Size" and looks up it's values in a Table named "Tank Size" and stores the one you pick say 2500. Now the problem. In the "Tank Size" table the row also has the price in the next column. So when someone picks 2500 in the combo box it will also list the price in say a text box or something next to the combo box. I hope i explained it o.k.
