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?
I'm somewhat new to working with ASP and very new to databases, MS Access, and SQL.
What works is opening my .mdb file, which connects through an ODBC DSN to get dynamic data. Nothing fancy.
What I'm trying to do is create a web interface via ASP to access certain data and fields in the db.
Here are the super-noob questions...Do I need a version of MS Access and the .mdb file on my webserver (where the .asp file is)? I don't have the ODBC DSN set up on the webserver (which is linux). Does that need to be done before anything will work?
Let me know if code snips would be of any assistance. Thanks much, in advance!
In the Access application that I have developed for a user, the application is supposed to establish the ODBC connection to an external database when the application is initiated. On my PC, the application works. On an older PC, the application works. However, on the User's PC and on the new one that we are building for her the linking to the external tables does not work. I have displays for the tables that she is to link to as the program is doing the linking. Sometimes, on the PC for her use, the first table will not link and the rest will. Sometimes, none of the tables will link. Sometimes, the first half will link and the second half won't. I am stymied. Below is the logic that I use to make the connections at the beginning of the process. Any suggestions?
Dim strTable As String
On Error GoTo Assign_Error
'MsgBox ("Click on OK and Please be Patient as the program links to PeopleSoft tables.")
' NOTE : Do not unlink the tables as you will have to manually relink the tables
End Function Function link_table(strTable As String) Dim dbs As Database Dim tdfLinked As TableDef Dim strDatasource As String Dim strDatabase As String
Set dbs = CurrentDb Set tdfLinked = dbs.CreateTableDef(strTable)
' tdfLinked.Attributes = dbAttachSavePWD ' Check to see if table already exists and if it does then do nothing ' For Each tdfLinked In dbs.TableDefs ' If tdfLinked. = strTable Then tdfLinked.Connect = "ODBC;UID=sysadm;PWD=sysadm;DSN=" & strDatasource & ";" tdfLinked.SourceTableName = strTable tdfLinked.Attributes = dbAttachSavePWD
dbs.TableDefs.Append tdfLinked DoCmd.Close acForm, "Message" ' Exit Function ' End If ' Next ' [Forms]![Message].SetFocus ' [Forms]![Message]![Message] = strTable & " Not Found for Linking" ' [Forms]![Message].Repaint
Link_Error: ' if the error is simply that the item to delete isn't actually ' there to delete, we want to skip it. If Err = 3265 Then Resume Next End If ' otherwise we want to show what the error is, and then exit. MsgBox Error$ Resume Link_Exit
End Function
Function unlink_table(strTable As String) Dim dbs As Database
On Error GoTo Unlink_table_Error
Set dbs = CurrentDb dbs.TableDefs.Delete strTable
Unlink_table_Exit: Exit Function
Unlink_table_Error: ' if the error is simply that the item to delete isn't actually ' there to delete, we want to skip it. If Err = 3265 Then Resume Next End If ' otherwise we want to show what the error is, and then exit. MsgBox Error$ Resume Unlink_table_Exit
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.
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.
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).
Before we moved webhosting company we could have external access to our MySql database which was great as our MS Access system would periodically pull data from our MySql site (namely customer enquiries which were entered via a form on our website) and dump them in our MS Access live quotes table all automatically.
With our current host (which seems to be the norm from my web-searches) they only allow local access to the MySql system.
My question is, how can I oversome this hurdle without having to move hosting company. I really don't want to move again as it's a real pain.
I have a little problem: And hope somebody can give me an answer.
I have two tables, one form and on the form I have two textboxes. One of the textboxes should be connected to ONE table and field, and the other textbox to the OTHER table and field.
I tryed to conect through the expression builder but had not much luck! See code below.
This code comes up in the ControlSource property section and textbox also: =[tbl_CompanyContact]![CompanyPhoneNumber] =[tbl_PrivateContact]![PrivatePhoneNumber]
Where do I set in properties the connection to different tables i.e. tbl_CompanyContact / tbl_PrivateContact and where the connection to the field CompanyPhoneNumber / PrivatePhoneNumber.
I want to know if it possible to use MS Excel instead of web application (ASP, HTML,...) that is connected to MS Access and will update MS Access as user update information on MS Excel?
If it possible how I should get started b/c I kind of have a template for Excel. I just need to learn connecting excel to MS Access and maintain them.
My office workstation took a very long time to connect to database in Access 2003 after upgrading to Windows XP, a few minutes need to be taken just to open a simple form which normally takes less than 10 seconds. In simple words, whenever it has to retrieve data from the db, it will be super lagging .
The rest of the workstations running on Windows 2000 were running perfectly fine.
The database is located on the host pc, which is running Windows 2000.
Initially we suspected that it might be because of the insufficient RAM. Thus it was changed from 1GB to 2GB. But even after changing to 2GB, the problem still exists.
Can anyone please advice me on how to check and rectify this problem? What can be the cause of this problem?
In addition to my Intro to Access class, I am taking a Web Programming class, which has the same general assignment, but for Web pages, instead of an Access database; create at least 3 pages, 1 each for financial data, customer relations and product/service info.
I would like to create a small Access database connected to a Web page. I won't have a server, but I can run everything off a computer. I have a book that tells me the steps to do all this, but I'm supposed to install MS SQL Server (I chose to download MS SQL Express Server), and I can't get Access to talk to it. Among other things, I noticed that I could not stop SQL Server, nor could I start SQL Browser. I did enable TCP/IP (I think). I uninstalled the whole thing, thinking I could start from scratch.
I have an access database that has fields that i want to be entered externally via excel. I want to be able to manipulate the data from access and excel. If you change in one, it will reflect the change in the other.
I want this to happen seemlessly, with a notification to either end when either end is changed.
Linking to an excel sheet from access doesn't seem to work because you can not change anything in the fields that were entered in excel from access.
I have also tried creating a connection from excel to access. I can change the data in access and it reflects in excel, but if i change the field data in excel, it doesn't reflect in access.
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.
I am coding an ASP front end for an Access database. I actually had it working yesterday but I still had some tweaks to make. My development has come to a stand still because of this crazy error I awoke to this morning. I went to the url of my ASP page and all of a sudden I get this error:
Microsoft OLE DB Provider for ODBC Drivers error '80004005'
[Microsoft][ODBC Microsoft Access Driver]General error Unable to open registry key 'Temporary (volatile) Jet DSN for process 0xbac Thread 0xc84 DBC 0x19e6fc4 Jet'.
So after doing some research, I decided to change my connection string to use Provider=Microsoft.Jet.OLEDB.4.0
Once I changed over to the Jet driver, I got this error message:
Microsoft JET Database Engine error '80004005'
Could not find installable ISAM.
I am totally stumped with this problem. I actually re-upped the database and it started working briefly but the error message soon returned. Everything I am reading is saying to change permisions and change some stuff in the registry but since it was working fine yesterday, I do not believe it is a registry setting.