Retrieving records from the MS-Access database

Question

Hi,
I am capturing an user input from a text field into a variable called 'valAuthor' and then using it in the following query statement.
stmt.executeQuery("Select * from BksTable where AUTHOR = 'valAuthor'");
But for some reason the records are not getting selected. I tried the above by replacing another field and another variable but it is the same. I checked for the variable 'valAuthor' to see if it contains a valid value before and after the statement and it does.
Say for an example the 'valAuthor' contains a value "Grisham" and when I operate the statement as:
stmt.executeQuery("Select * from BksTable where AUTHOR = 'Grisham'");
it works fine. I even tried to replace the = sign with LIKE. But no luck and I have spent morethan 10 hours on this and feel depressed. Any help, please?
I am using MS-Access 2002.

Answer 1

Hi all
Just a bit more explaining here about parsing
statement.A bit more explaination about the real world.
>
When executing a query, EX "Select col1 from tab1
where col2 = 'ABC'" will be parsed the first time it
is executed.It might be. It depends on the database and driver.
And with Access it doesn't.
>
If I now execute the same query, EX "Select col1 from
tab1 where col2 = 'DEF'" it will be parsed again!.
Remember it looks at the complete string that is the
query statement and because query 1 and query 2 has
different character in it it will cause a new parsing
action. Even upper/lower case changes will do this.
Using preparedstatement will force the compiler to use
Bind variables, thus substituting the value of the
variable only. Thus only the first query will be
parsed if it is not in the SGA yet. Subsequent will
not parse the query string as it is already in the
SGA.
It doesn't have anything to do with the java compiler.
The effort to use PS can be wieghed against the number
of expected executions. If the query will be run one
or two times per day, no problem. If running more than
say 4000 times per day, big performance impact.
Remember the SGA will remove the oldest parsed
statement to make place for a new statement that is
parsed, thus once the SGA's sql area is full, you will
have a lot of statements removed that can be a big
overhead to parse again if they are needed.
Yes. And the most likely time that the cache will flush is in an enterprise system where using a prepared statement would have the most impact.
Holding on to a prepared statement to do 4000 for the entire day is NOT a good idea.
Holding on to one while you process a batch of 4000 might be.
Do a select from the SQL area of the SGA and check.
Bottom line, PS is the preferred option for
perfomance.How do you do a select in MS Access for the SGA?