Hi experienced programmers,
I'm surprised with the SQL qry which follows:

PARAMETERS [tblDadosIN]![CodigoNome] Long;
SELECT tblDadosIN.CodigoNome, tblFuncionarios.Nome, tblDadosIN.Data, tblDadosIN.Dia, tblDadosIN.Ocorrencia, tblDadosIN.HExtra
FROM tblFuncionarios INNER JOIN tblDadosIN ON tblFuncionarios.CodigoNome = tblDadosIN.CodigoNome
WHERE (tblDadosIN.CodigoNome)=[tblDadosIN]![CodigoNome];

my tblDadosIN is a table where the parameter that is filled
when prompted happens four times ( four rows). Although when
i run the query above prompted by the parameter
the datasheet displayed as the result qry has five times
more rows than the source table (twenty rows). Would some one
be pacient enough to teach me the right road ?:(
Rgds Penta.

I'm not much help with parameter queries. Never really use them. (As you may have gathered from your prior query about your report and the form.) Therefore, I'm not really clear about what you're trying to accomplish.

But I'll take a guess here. Since you are INNER JOINing, maybe you should put tblDadosIN first....

FROM tblDadosIN INNER JOIN tblFuncionarios ...

Just a guess that tblDadosIN has to know the criteria for each record it's trying to join with tblFuncionarios.

I don't use PARAMETERS since they seem superfluous to me (except that PARAMETERS will validate that user input is Long). You could simply leave off PARAMETERS and get the same result... if you want the user prompted to enter [tblDadosIn]![CodigoNome].

What confuses me about your query is that the WHERE clause is essentially saying, "give me everything in tblDadosIN". That is, except for the fact that you've tried to declare "[tblDadosIN]![CodigoNome]" as a parameter, "tblDadosIN.CodigoName" and "[tblDadosIN]![CodigoNome]" mean the same thing in an Access query. I don't know if the fact that you've declared it as a parameter overrides the functional definition which means, give me the value of the field CodigoName from table tblDadosIN. Perhaps because you have declared it as a PARAMETER, it thinks it has to ask for a value?

Just curious... why do you use PARAMETERS in your queries? If you're building code to use the queries, why not just build the SQL statement and substitute the parameters in the SQL? If you're trying to control the data that displays on a report or form, just set the filter criteria for the report or form. If you're trying to control what displays on a subform or subreport, just use the Master/Child link fields.

I suppose I should learn more about PARAMETERS. Maybe there is a really good use for them. But as I recall, the last time I tried to use them (so many years ago) I gave up in frustration because I kept getting problems similar to those you are having.

Randall J Weers
Membership Vice President
Pacific NorthWest Access Developers Group
http://www.pnwadg.org

Thanks u Randall for ur care,
I had this unexpected behavior on an apparently elementary task and thought
that it was something wrong i was doing. I have been learning SQL recently
and i think i read something about the odd result on a book which is not
on hands. If i find something about the behavior i'll let u know. I've been
using parameters before i create a criteria form as a step for building
a desktop application, and i'm addicted to MS ways of doing things with as
few coding as possible.
Rgds Penta.:)

Again on the same subject,
I've tried to run the query without the parameter using the criteria directly
on the qry grid and it worked OK. Paying much attention on the wrong result
i've had before i've missreported the result. When i run the parameter qry the
result is the whole table.That is the parameter is not filtering at all.
Trying to fill the SQL directly with the parameter value as an alternate way for instance, and go back to the qry grid and try to run the query i've had an error on access which stops working. Yes, as Randall says parameters dont seem to be reliable.
rgds P.