Hi! I have a query setup that feeds off of three combo boxes on a form. It is setup to allow a user to search and calculate revenue for a selected time period by company, then department, then page. If all three or just company are selected, there are no issues running the data. However, if only company and department is selected I receive an 'ODBC--Call Failed' message. The issues seems to be stemming from the department field as I can link the department table to the main table and the query will run without error. The problem with that bandaid is that the query takes more than 15 minutes to run that way as opposed to about 2 minutes to pull more data at the company level.
Any suggestions on why this is happening or a fix that can be put in place? Any help is greatly appreciated.
When running a query in Access 2013 or 2010 we get an ODBC call failed. However when we run just the form, which the query connects to, it works just fine.
I have a new user who is trying to connect wirelessly. I set up the ODBC connection on his laptop but when he tries to run a report that uses queries looking at linked tables he gets ODBC call failed. Is it because he is trying it wirelessly. I'm just the data guy so I don't know too much about networking.
I have a standalone Access DB with 4 linking tables therein. They all point to tables that are stored in a server Access DB. I can open 3 of these tables in datasheet view without any problem, except one. Whenever I try to open it, I am prompted following msg "ODBC call failed etc... server API error (#669) etc..." And when I click OK to close the Error msg box, then another msg box appears with the msg: "Microsoft Access can't open the table in Datasheet view"
I've deleted the link table and recreated it. But I still can't open the table in datasheet view. Does anyone knows what's to do? :confused:
I am running Access as a front end to SQL and maintain all reports and forms from a .mdb. I then release an .mde to a different location for end users to use.
Each time I release an .mde and a user attempts to run a report an "ODBC call failed" error appears. So I have to re-link tables on users pc's. The Users ODBC connections are set up the same as mine.
I am facing a problem with ODBC call failed error latly.The problem doesnt occur on my development PC but only on other PC's.I'm a beginer in Access, vba and I cant find a solution to make it work on every machines.
Code:
Dim qSQL As String DATA = "#" & DatePart("m", DATA) & "/" & DatePart("d", DATA) & "/" & DatePart("yyyy", DATA) & "#" qSQL = "SELECT Sum([IL]*[TO])" & _ "FROM PUBLIC_S INNER JOIN PUBLIC_SD ON PUBLIC_S.U = PUBLIC_SD.U " & _ "WHERE (((PUBLIC_SD.DAT)=" & DAT & ") AND ((PUBLIC_SD.ANA)='" & ANA & "') AND ((PUBLIC_SD.IA)='" & ia & "') AND ((PUBLIC_SD.AN_C)='PIMSS')); Set Db = CurrentDb() Set rs1 = Db.OpenRecordset(qSQL)
I have an ODBC connection to our company's data that uses Macola. I can enter criteria in the fields in Access to filter that data, but when I try to put a parameter query in such as [Enter order number:] I always get an "ODBC-call failed" message, error# 3146. Can I even solve this problem, or am I just not going to be able to actively change the criteria unless through a pivot chart or table, or by hand? Can anyone help? Thanks.
i am using access as a front end to SQL Server 2005 and link tables via ODBC.
Today when I run a query (normally works fine) I receive an ODBC Failed message box. I have tried opening each link table connected to the query and can open fine.
When creating a query I have set up a parameter query as instructed (in this case searching for a name) but when I run the query it returns the error 'this expression is typed incorrectly etc.'
I have worked out that this must be due to the fact that the names are not typed in by a front-end user but need to be chosen from a dropdown list (which i have stored in a separate table) - So, the query seems to fail based on that.
I have an access 2002 front end and I am linked to a sql server express 2005 backend and in one of my tables I am getting this error when I add a record to a work order table. The error is ODBC connection on INSERT failed on linked table.
A few strange rhings happen. It only involves customers with over (approx.) 140 work orders (there is a one to many with customer to work order). All other customers seem to be immune to this.
Also, if you go to the tables directly from a access database window, you can still add/edit or delete records, but in the form view, it gives you an error.
I have tried several things including changing code (the orgional code was set dbs= currentDB and dbs.execute("INSERT.......)
I have found similiar posting but no real direct causes. does anyone have any ideas on how to resolve this?
Hi All....getting an "ODBC --call failed" error when trying to re-link tables in the Linked Table Manager in Access. I'm having a problem connecting to one particular Oracle database. I am able to connect to other DBs with no problem.
I can also connect to the problem database through SQL Navigator. And I've been able to connect to it in Access in the past. Any ideas?
I'm having to recode some old MS Access DBs so they will run in the following environments:
Office 2000 on WinXP Office 2003 on WinXP Office 2010 on WinXP Office 2000 on Win7 Office 2003 on Win7 Office 2010 on Win7
When I wrote my code for Office 2000 on WinXP things were simple because directory paths were the same across all computers and I could hard code pathing when using a shell command to launch other files.
My new approach is to make a function call to the Windows registry to determine the default executable and path for opening a file based upon its extension (see apicFindExecutable in basWindows API module).
I'm able to use code to create a shell call and debug print it to the immediate window. If I put my cursor in the immediate window at the end of the shell call and hit [enter] the external file will open as desired. If I try to open the external file directly through code, I get a file not found error.
To recreate the error take the following steps:
(1) browse to files that are accessible from your computer (2) click the PREPARE DATA AND OPEN MAIL MERGE DOCUMENTS command button
Shell function call is made by the fnOpenFile function located in the basOpenFile module. There has to be a trick here that I'm missing.
I am tyring to set up a query, that runs from a selected date range, to return only the records that don't meet the requirments. For example, I have four fields:
Name Date Attended Required
I want to start the query from a date range usesing Between [StartDate] And [EndDate]. There are mulitpule records containing the same date. Then from there I want to return only the Names that don't attend the required number of sessions.
Ex. Attended = 2; Required = 4; Return name Attended = 3; Required = 3; Don't return name
Would this be possible with one query? If so, how would I go about setting up the criteria. If not then how would i link the 2 queries together?
I want to track which user has which phone and track issues with them.
I have all the relationships set up right.
I have tables:
DeviceStatus - for the drop down box, contains IT Stock, Faulty, With User and Retired DeviceTypes - Contains model numbers for devices Assets - Contains a link to DeviceTypes, a link to DeviceStatus and the serial number of a phone.
I have a query:
StockStatus - shows Assets.ID, DeviceStatus.Status, DeviceTypes.description and Assets.SerialNumber
What I want as an end result is a form with a drop down box that shows DeviceStatus.Status (which I have working at the moment) with a go button next to it which will call the query that only shows what was selected in that drop down box.
I have a form whose data source is a select query, q3, that is built from 2 other select queries. I'll call them q1, q2, and q3. q1 is a parameter query where I enter a "Cutoff Date" that the 3 queries manipulte and generate the desired results that appear in the form. The problem is that I don't know how to capture the parameter "Cutoff Date" from q1 to display on the form.
hi, i have a query which when the user selects a value in a combo box it pulls up the other details of the item, such as price.
i have noticed though that if i try and enter a new item into the list, through the combo on the form and then enter a price, it gives me error 3101 (something to do with not being able to find the record.
i assume this is because it is trying to locate the chosen item of data within the main table and pull up a price.
I am trying to run a query in Access 2010 but I am getting an "Invalid Procedure Call" error. I searched online and found that this error can be caused by broken references.
I opened the VB editor (Alt F11) to search for "Missing" references but I do not see any. These are the 4 that are checked.
1. Visual Basic for Applications 2. Microsoft Access 14.0 Object Library 3. OLE Automation 4. Microsoft Office 14.0 Access database engine Object Library
I built a database off of the access wizard and it gives me the capability to enter date parameters before running my reports, than displaying the revised report. I.E. I am prompted to enter start and finish dates, and then after entering this info and hitting a button to preview the report, the only data displayed is that that falls into that date range.
I have created a new report that wasn't built into the wizard. This report "hits" an underlying query. I have also added a button on the switch manager to preview the report. I want a user to be able to click that preview report item on the switch manager, then be prompted to enter start and finish date information, then hit an ok button, then have the report with the relevant information displayed.
Any and all help would be greatly appreciated. Thanks.
The program I am working with has an option to add a new record to another table using a button. Not all the records, even new ones, need to be appended.
The append query works fine in all situations but one--when a new record is entered and saved, the append query button returns 0 records to be appended. However, if you go to a different record and come back to the one just added in the main table, the append query works fine. The query uses a TempVar to select only the record being seen at the time. The TempVar is declared prior to attempting to append the record to the other table.
Is there a way to make a just entered record act like its been around for a bit (well at least to save it by changing record to another and back)?