I've seen that before when using MS-Access. If one of your field names is unknown, then MS-Access considers that field a parameter and generates this sort of error. It can also be another identifier, other than a field name, something that MS-Access cannot lookup.

Make your query as simple as you can, just select * from table and then add more in until you start getting the error. Or perhaps print out your query/insert and try it directly in MS-Access itself.

" dont know y its giving me this error. All the parameters r correct. Can any 1 help me. Im developing a container tracking system for a company. I have worked with Java and Oracle. This is my first time with Java and MS Access."

You saved yourself 7 characters by writing that nonsense "y, r, 1". Was that really worth it?
If you consider yourself a professional (which you seem to do), don't use such shorthand language.

And oh, for a production application NEVER use the JDBC-ODBC bridge driver from the JDK. It's for demonstration and testing only, too unstable and poorly performant for realworld use.

Respected Sir, Thank u 4 ur kind help and ur reply is highly appreciated. I kind of solved the problem my self yesterday. I did not close the single quote :o . Thanks anyways. Is there some other method for connecting Java to Access so that it can give meaning full and specific error messeges ?

If u could read carefully ( instead of searching for short hand writting ) I never said nor proved nor implied that I am a professional. I am an Internee and we tend to gain experience not to Show Off ( which u seem to be doing ). Please consider the following link.
www.orkut.com

P.S U still did'nt give me ur "Professional" Answer for the Problem.

I consider correct use of language to be extremely important for people creating software.
After all, software is a description of what a computer is to do written in a language.
If you can't even be bothered to use natural language correctly to communicate your thoughts, you probably don't bother to do the same to that computer.
And if you're incapable of communicating in natural language, you're also incapable of learning the skills needed to communicate with that computer effectively as those skills are passed along in that natural language.

Given that there is a highly disturbing trend of people incapable or unwilling to communicate in natural language using that language correctly and that trend coincides with a similar trend of those same people failing to write software that works, there does seem to be a strong link between the two phenomenon.

If u ever learned a programming language ( which I doubt ) there is a big difference between a Programming Language Syntax and Natural Language. There R NO SHORT HAND WRITTING embeded in a programming language or designed like r,u,y etc for writting software code or Instructing a computer to do a certain task. But Still What ever makes u happy. Keep ur "PHENOMENA" with u. There is a rule of thumb for using any Natural language and that is MANNERS which u lack big time.

I've read this and consider that jwenting has actually made effort to be polite in communicating what might be a tad off topic but nevertheless a very valid point. In any professional circle (and by professional I mean workplace, not simply trained and qualified people) the use of SMS or IM style abbreviated language is very much frowned upon.

It portrays a quite negative impression of you, and jwenting is only seeking to help you avoid that happening.

I don't know what this whole thread is about, and I prefer to stay out of it, because I don't do well with insults and flame wars, but I just wanted to add that when programming, there are often an infinite number of ways to do a particular thing. Not only are there an infinite number of algorithms to do a task, but there are an infinite number of ways to execute (code) an algorithm. Not only that, but syntax / shorthand does exist for programming code. For example, in the C++ language, can also be represented as in addition to as Just a shorthand way of writing it

Yes, but it's shorthand that's part of the language specification.
It's like writing e.g. instead of "for example".
If I were to write "fe" when I mean "for example" noone'd understand me, right?
Same if I were to write x+; when I want to write x=x+1; the compiler will complain