My office computer, along with the phone system, printers etc took a lightening strike last week. The hard drive survived but not the computer. I was able to get the office access db onto a new system but now I get errors when running it. When opened, the main menu appears. Whoopee!Not so fast. When I select an item, I get "the expression On Click you entered as the event property setting produced the following Automation error. The expression may not result in the name of a macro, the name of a user-defined function, or [Event Procedure]There may have been an error evaluating the function, event, or macro"
Pressing the button a second time does not produce the error and opens the correct form.This form works properly. The second problem is with a second report form that opens properly.This form expects dates and accepts them but when I try to print the report, access closes with no error message.
On certain machines when the user clicks a button the click command performs an openreport event procedure in print preview. Access then crashes saying it encountered errors and will close. When I change the click command to open the report by a moacro the report opens fine.
Problem: Access crashes during data input in a certain form. – Not always on the same field, and not always on the first record. Sometimes I can input 2 or 3 records and it crashes on the 4th. The "modul" that the crash shows is always the msjtes40.dll
Action taken so far:
1.Checked the version of the msjtes40.dll – it’s the latest
2.reregistered the msjtes40.dll
3.Created a new DB imported everything
4.Repaired the Db
5.decompiled and compiled all the code (which I have been through with a fine comb - there is no complidated VBA on the form at all.)
6.recreated the form entirely
7.Checked the Source of the form for any funny records
Hello.Your help is very much appreciated.I am using ACCESS 2002 (XP).I have two access files - one program (with link tables) and the other one is the database.I created ACCESS report.When opening the report for viewing - it's all good.(DoCmd.OpenReport "_rptDetails", acViewPreview)When trying to save the report to a file - Access saves it to a file and immidiately crashes.(stDocName = "_rptDetails"DoCmd.OutputTo acReport, stDocName)when printing - it prints and crashes(stDocName = "_rptDetails"DoCmd.OpenReport stDocName, acNormal)I tried:1. To make the data source of the report a table instead of a query.2. Complied the code again.3. Copied everything into a new database.4. Created a new report from scratch.Nothing helps.Would you have any idea of what causing the problem?Thank youRoy
On certain machines when the user clicks a button the click command performs an openreport event procedure in print preview. Access then crashes saying it encountered errors and will close. When I change the click command to open the report by a moacro the report opens fine.
Hi all, Forgive me if this is in the wrong forum. I have a colleague who has a problem where Access 2003 crashes every time they try to export a table to Excel 2003. It doesn't matter what mdb is used Access crashes.
I've run into a big problem recently. Whenever users run a specific query they receive an error that says, ACCESS has encountered error and will be shut down. the exact error message is shown below:
Microsoft Access has encountered a problem and needs to close. We are sorry for the inconvenience.
I have been having this issue with two different versions of Access, firstly XP and now 2003.
The issue is every time I open a blank database, and click on the "create using wizard" option, access crashes while trying to set up the wizard. When I view the dump rep, it all seems to point to msaccess.exe.
I am trying to export a table out of Access to a dbf. However, when I do this Access crashes and shuts down. I am able to export the table to any other format also I am able to export the table to dbf from another computer. My setup is XP Pro SP 2 with Office 2003 SP 3. I just moved from SP 2 to SP 3 hoping that would solve my problem, but it did not. I have tried uninstalling and reinstalling office, detect and repair and a different user profile. Any suggestion would be great. Thank you in advance.
If I already have an Access database open (sometimes I've forgotten about it), when I try to open another one from my desktop, it maximizes the first Access window, and then my computer freezes--I have to CTRL-ALT-DEL and close both of them through Task Manager to continue.
I have never seen this happen on anyone else's computer. Does anyone know what is causing the problem? It is not any one database; the problem occurs no matter which are opened.
I've just set up my Access on a new PC and now when I try to connect to my MySQL database through odbc, Access crashes without any error messages, just the standard microsoft error reporting message.
I am connecting Access to QuickBooks with the QODBC. I tried to do this in MS Access 2010 with Windows 7 and it worked fine. Then I tried it on a new computer with MS Access 2013 and Windows 7. Now, when the VBA gets to the line:
oConnection .Open "DSN=Quickbooks Data;OLE DB Services=-2"
It crashes. No message, other than the generic "Access has stopped working" message. I am using ADO for the oConnection. I am not sure what the problem is or how to diagnose it. I have used an ADO connection to connect to Excel, and that worked fine, so my guess is it have something to do with the DSN connection?
We have run into a problem with Access 2013 when trying to print reports. The program always crashes. Have updated printer driver for the HP LaserJet P2035.
On open I change the Picture property of an image control to another image. I do it 2 places. Access crashes on the first change or on the second. In about 50 % of the cases.
We are running many MS Access databases in a mixed estate - mostly Windows XP terminals. The databases are split with the front end on the desk top and the back ends on a server running Windows Server 2003. We have a chronic problem of crashes when users go back into memo fields to add data - all text. The problem is intermittent, not possible to reproduce and varies in frequency.
Without having made any changes to my setup, Access now crashes when I try to open a Macro in design view. I have checked the Trust Center and the folder where my database is stored is trusted (including sub-folders).
I have DB in access 2007. I have a report that is uses a select query to generate the information for the report. It has been working great, But however lately like maybe with in the last month, it has been causeing Access 2007 to crash. I am having the same issue with another DB that uses the same information but that information is imported in. both Databases have worked great up until two months ago. Microsoft states that it is because of the program. I have tried to repair the DB by using the Repair option. I am confused as to why this would be happening. I can create a new report and it seems to work. but I do not want to change all the DB on everyone's computer just for this reason. I also have two buttons on my report that utilize macros to close or print the report.
Since we have installed the latest Windows critical security updates, upon closing an Access database, the database gets corrupted. Error code is c000020c.
I did a search on common access errors and other errors that you would want to trap and got the following results:
Cannot update. Database or object is read-only Operation must use an updateable query General error Unable to open registry key Could not find file Could not use '(unknown)'; file already in use Table 'tblTable' is exclusively locked by user 'Admin' on machine 'MyMachine' Too few parameters. Expected 1 Either BOF or EOF is True, or the current record has been deleted Item cannot be found in the collection corresponding to the requested name or ordinal The search key was not found in any record
If you know any extra errors, can you please add them to this list?
I have recently done a fresh install of access 97 to our 2003 server. I load up an access app, it brings up a form with a button...I clidk the button, and it closes the app with no errors, and leaves the ldb file in tact. Checking the event viewer, I get this message:
Faulting application msaccess.exe, version 8.0.0.5903, faulting module unknown, version 0.0.0.0, fault address 0x00202878.
It appears to be on the buttons that open forms / reports, but not those that run queries. Any ideas?
I have our primary web based inventory system that I am exporting to Excel and using this as an import to Access for the main raw data for my database. This being inventory it changes daily so I am updating this table every day. When I try to append the table it ads all the records. I am wanting an easy way to add only the new records/take out the ones that are no longer there. Basically update the table with what is currently there.The only have I have found to do this is by running non-matching queries and update queries.
Hello everyone. I will admit I am a novice when it comes to access. But I do have some programming background in Lotus Notes. Now maybe its just me but Access seems to error out ALOT and I keep getting messages like:
-File is not a databse -A user unexpectedly shut down access -Some c++ runtime errors
I just dont understand what I am doing wrong. I am saving my work like I would do in anyother program. But at least once a day I have to resort to a backup copy because I keep getting errors like the ones above.
I have created an access 2000 DB and it did the same thing about 2 weeks ago...been doing it at least once a day if not more. I have created new db's and still the same thing. I have even converted it to 2003 and still problems.
For example I created a report and was told I didnt have permission to access the report??....WTF..I am the only user in the db as its in development...I created the db..if I dont have permission WHO does. So I tried to add myself in permissions.....then that when I got the c++ error.
I have been working in Notes DBs for the past 6 years and I have to tell you access doesnt have ANYTHING on notes. I have never had such stupid error out of the blue in any program I have used...I mean just closing the DB is causing an error on some days...
I am so frustrated with this its beyond belief..I have a real hard time turning this crap over to my users when I DONT trust it will be running next week...UGH
Some guidance will be most appreciated as I am about to just drop the project and start from scratch in something else.
this is the code that im using to help me with a listbox and a search text box that is embedded on my main form. it works ok. The problem is, i was trying to link an already filled out Table with data to this interface.
When i key in information from the form it works, but when i just enter stuff through the table (which was already completed and handed to me) When I click in the listbox on the main form the code window just pops up showing this section of my code. Help./
I'm not sure if this is an Access problem or an ASP problem or even an IIS problem, but I have to start somewhere, so here I am. Ok, this is the deal. I've got an Access database that I'm using to store login/password info (just a training thing, I'm new to ASP) and I've successfully created a login form and an ASP page that determines if the username/password combo is correct. If the info is legit, it forwards the user to a success page. If the name is good, but the password is bad it tells them so and makes them try to log in again. If the user name doesn't show up in the database it says they must register and forwards them to a registration page. All is fine and dandy in my li'l ASP world. Except for one small problem... When testing my few pages I keep getting an "Unspecified Error" that always points to this line of code:
Far as I can tell, what's happening is that every time I access the database, I must wait a small amount of time (seems to be about 30 seconds) before I can do anything with it again, or I get this error.
Let me clarify, When testing, I would go to the login page, type a correct user/pass combination and then I get forwarded to the success page. Cool. I go back to the login page and try it with a correct username, but an invalid password.... oops, I get this error. If I wait about 30 seconds, I can go back to the login page and try again and everything is fine. The order I test in doesn't matter...
Correct Combo -> invalid password invalid pass -> non existant user correct combo -> correct combo etc...
Doesn't matter. Once I access the database via .Open it seems that I can't do it again for a while. Why is this? I use a .Close on my record set and then I set the recordset and connection objects to Nothing *BEFORE* each and every page redirect.
Hi guys . i wonder how i can trap the following errors in access 2000 forms. I have the database tables in sql server 2000 and front end is made by access 2000 forms. I be happy if some one show me how i can trap these errors and promt aproperte message to the user when they violate them using forms.Thanks
1)Violation of not null constraint 2)primary key violation 3)Trigger violation 4)and other erros
I'm having trouble opening up the tools I am developing in Access for multiple users. I split all my databases so the users will only interface with the "Front End" and I just tried saving one as an ACCDE file. I had the ACCDE file open on my machine and asked another person in the office to try opening it (all our files are stored on a network drive, which is already identified as a trusted source).
She got the following error message:
"The database cannot be opened because the VBA project contained in it cannot be read. The database can be opened only if the VBA project is first deleted. Deleting the VBA project removes all code from modules, forms, and reports. You should back up your database before attempting to open the database and delete the VBA project"
How do I fix this? I don't want to publish several Front End Access files since each person in my office will ask me to customize their file and my supervisor wants everyone working off the same file. I thought the point of Access was that multiple users could open the same file and make data modifications. How do I achieve this while retaining all the fun, creative VBA solutions I have developed?
