Running Parameter Requires Table ID# Not Field Name

When I try to set a parameter for my inquiry, Access is looking for the table ID# instead of the text in the field I'm looking for. e.g:

Table - Inspection Results
ID Inspection Results
1 Pass
2 Fail
3 Non-rated

When I run a parameter inquiry requirement to look for inspection results, and I type the word "Pass" in, I receive an error. But, when I type "1" in, I get the information I'm looking for (all records with inspection results that were a "Pass"). Why is Access looking for the table ID number instead of the text value?
Could it be because the ID# is set as the Primary Key?

Sponsored Links:

Related Topics

Running Parameter Requires Table ID# Not Field Name
When I try to set a parameter for my inquiry, Access is looking for the table ID# instead of the text in the field I'm looking for.

eg:

Table- Inspection Results

ID Inspection Results
1 Pass
2 Fail
3 Non-rated

When I run a parameter inquiry requirement to look for inspection results, and I type the word "Pass" in, I receive an error. But, when I type "1" in, I get the information I'm looking for (records with inspection results that were a "Pass"). Why is Access looking for the table ID number instead of the text value?

Could it be because the ID# is set as the Primary Key?


Passing Parameters to a Query Without Parameter Prompts
I have a query that requires a parameter to work. I need to pass a form field (entered by the user) to the query as the parameter, but I don't want the parameter box to pop-up asking the user for input when the button is clicked to run the parameter.

I tried using DoCmd.RunSQL, but, if I understand correctly, this can't be used for a select statement. I used it with updating and inserting with no problems.

I'm trying to use qdf.Parameters() now, but I still get the popup. Is there a way to pass parameter without the parameter prompts?


Can I use a query in VBA if it has a parameter?
me? I'm using Access 2007. I have a query which uses a number of sub queries in order to build up its data. A couple of the sub queries use a control on a form as to get their parameter (i.e. the year).

Everything works fine, except that now as well as displaying the data on the screen, I would also like to write it to a table in order to keep a historic record.

It seems logical to use the same queries which already give me the data I require. However, every way I try to use the queries in VBA I get an error which says "Too few parameters expected 1". I have tried running the query by using dbs.execute, and I have tried opening a recordset with the query as it's source. Same error each time. The form is always open, and the control is available, so surely it should be able to get the parameters it requires?

It seems that I cannot use a query in VBA if it has a parameter. Is this correct? Can anybody suggest a solution


How to compare the field name as per parameter value
I want to update one table field from other table through the passing of parameter. If I pass the parameter 30/11/2011, the numeric field of the table [Nov_A] should be updated as per the other table's numeric field [Nov-11]. same like for December 2011, January 2012 and so on. I have written some code is showing the following error.
Run-time error '3129'


Excel passing parameters to Access for queries
I've got a piece of code in Excel which links to an Access database and runs queries in it. Some of the queries need parameters which are being passed to it using this piece of code:-

If param1 "" Then cmd.Parameters(0) = param1

The query I'm running requires 1 parameter which is contained in param1 (and I've stepped through the code to make sure it's there).

When I try to pass the parameter, Item cannot be found in the collection corresponding to the requested name or ordinal

If I miss out the the line of code above (leaving the parameter empty) and try to execute the query, I get the following error message:-
Too few parameters. Expected 1

It looks like I need to pass the parameter, but when I do it isn't accepted.


Parameter prompts twice but exists once
Running on Access 2000. A query has one parameter in it in the supplier criteria row It is the only criteria applied to the whole query.

Parameter was defined as.

Like [Enter Supplier Name or Part of Name or Blank for ALL] & "*"

The parameter is only in the query in one location.
It is NOT part of a calculation
It is NOT defined in the Parameters list (maybe that is part of the cause)

The issue occurred when running the query on its own. The parameter question was requested twice although only referenced once.

If the query was edited and saved the problem went away. But later for no reason it then appeared to return.

The only thing I can think of is that the database had not had a compact and repair for some while. I have now made them do this and will see if the issue still arises.


Referrence a field rather than a parameter
Having a problem completing a calculation in a query: When I type in a field name (enclosed in square brackets) in a calculation, things look fine. But, when I run the query, it treats the field name as a parameter and asks for the parameter's input. How do I get access to use the quantity in the referenced field for the calculation rather than ask for parameter iput


conditional formatting in parameter query
I am using a parameter query. Criterion field has
< [enter your value]
so after running the query, I want all values less than input value to be marked in red color/background. please suggest how to do that


Passing query parameters (in Tables) where the parameter varies
I know how to do this with Forms. I'm also aware that it is bad practice to use lookup fields in Tables. and by experimenting to find out how stuff works. Don't jump to the conclusion I am trying to use this technique for a finished job, I'm not.

Basically, PLEASE no 'don't use lookup fields in tables' lecture. I have readthat on SO many posts,

[Totally by-the-way, but why do Microsoft offer lookups as fields in Tables,]

Anyway, if you do write a Select query in a table field with a WHERE clause, and within the WHERE criteria you reference a parameter, and you keep it numerical, it works.

But if you ask the query to take this parameter from another field in the same table (because this parameter should vary depending on the record), Access won't have it. It gives a parameter entry prompt.

It is as though when you reference another field for the parameter value, Access doesn't understand that the parameter varies, doesn't understand that the user wants it to look at the PARTICULAR RECORD for a PARTICULAR VALUE for the parameter.

It seems to want either a general value for the parameter, Would there be a third way? and if so I'd like to know what.


Display Query Value That Requires Input Parameter
I have a query that returns a single aggregate value based on the input
parameter. I can't figure out how to display this on a form. The parameter I
want to pass to the query is the primary key from the current record. Any
ideas on how I can do this automatically? Or is there a better way of getting the value, I used a query because it's a distinct count function


Parameter Query - if Null show all
Im running a parameter query and I need it to show all records if left blank by the user.
I can achieve this but I cannot achieve it for more than one parameter.
How do I go about this?

Basically, if the user enters a value for the first parameter and enters nothing on the second one, i'd like to see all values for the first parameter


conditional formatting in parameter query
I am using a parameter query. Criterion field has "< [enter your value]" so after running the query, I want values less than input value to be marked in red color/background.


Using Combo Boxes as a Source for Parameter Queries
I often encounter a situation where I want to run a select (parameter) query on a particular table, but instead of having the user type in their own parameter, I'd like for them to be able to choose, from a combo box that auto-completes, the actual item in the underlying table, then use this string as the basis for the parameter query. I want to limit the parameters to already-extant items in the underlying table and so avoid close-but-not-exact matching problems by free-typing the parameter.


Drop-down list n parameter query
My users find it hard to use my parameter queries because they have to enter exact spelling. If the field that has the parameter value is driven by a list or table, is there a way to providea drop-down with the values for the user to choose from?


Designing a query with a parameter and a lookup field?
I'm designing a query. I want to include the field "Location". "Location" in the table I'm quering (is that a word?) is a look-up field, so that my people can just click on their choice from a list of locations.

I want to have a parameter in the query so that they can specify which location is to be used in the query. But when I drag "Location" from the field list into the query design and put the following in the criteria section it doesn't work: Like [Enter location]&"*". When I run the query and type in a location at the parameter prompt I get no records.

I'm wondering if, since "location" is a lookup field in my table, the parameter will not recognize a "typed in" location. Do I have to enter a different phrase in the criteria to perhaps access the same lookup list that appears in my lookup field in the table?


Running Multiple Queries Simultaneously?
I need help with running multiple queries that are in relation to each other to perform one function, in addition to that, being able to use one parameter in those queries performing one function.

ATM I have to click each query and input the same parameter 2-3 times. It is quite painstaking to do. Everything in my database is functional, I just couldn't find a way to shortenit.

One function has different types of queries: Update, Append, and Delete.


Send parameter to Macro from VB
I have a macro that imports data using the TransferText Action. I want to pass the "File Name" from my VB code as a parameter. Currently having to hard code the file name in the macro, but want to pass it as a parameter.

Here is my code for running the macro.

DoCmd.RunMacro "importlead"

I want to have a field on my form that allows them to enter the filename and path and send it to the macro.


Make table query -> table name to be the parameter
I have a make-table query with a parameter. I have a function which does the following:
1) ask for a new table name
2) start running the SQL query
3) the SQL query asks for a parameter
4) the new table is created with the new query data.

Here is the code:

Function CreateTable()
Dim NewTableName As String
NewTableName = InputBox("Please select new table name")
If Len(Trim(NewTableName)) 0 Then
DoCmd.RunSQL "PARAMETERS KockKod Text ( 255 ); SELECT [Kockazatok-proba].RiskID, [Kockazatok-proba].[Risk name], Nevek.Vezetknv, Nevek.Keresztnv, Nevek.[Harmadik nv], Nevek.[E-mail cm] INTO " & NewTableName & " FROM [Kockazatok-proba] INNER JOIN Nevek ON [Kockazatok-proba].Nevek.Value = Nevek.Vezetknv WHERE ((([Kockazatok-proba].RiskID)=[KockKod]))"
End If
End Function

My problem is that the table name is the parameter, so is it possible to make the code to make a new table with the name of parameter, without prompting me for a new table name at the beginning.


MS Access 2000 parameter queries
Can anyone help me with a problem I'm having running a parameter query in Access 2000 ? I have a table that has a date/time field that I need to query, based on user input. I want the user to be able to select a date and retrieve all the items received on that day. Problem is if I use the notation =[Date?] in the criteria box in the query design view, it returns no results, even though there are records that should be returned. What is the correct syntax I should be using ? If anyone can point me in the direction of a tutorial I'd be grateful.


Running a stored parameter query from a form without pop up boxes.
I know that you can create a query with sSQL = some SQL statement

me.recordsource = sSQL

I have looked at other threads that have talked about using forms!myform!mycontrol as a parameter this is good but limits the query to one form.

I remember that there was a way of calling a stored parameter with something like.

me.recordsource = qryPlanned With mdate1, mdate2