Dataadapter.fill data type mismatch in criteria expression.

Question

0.00/5 (No votes)

See more:

, +

I Don't know what is the problem With that code really!

<pre lang="vb"> Dim XID As String
        XID = FormSuppliers.txtcode.Text


        DataSetSuppliers.Clear()

        SQLSuppliers = "SELECT * FROM Suppliers WHERE SN = '" & XID & "'"


        If Conn.State = ConnectionState.Closed Then
            Conn.Open()
        End If

        Dim DataAdapterSuppliers As New OleDbDataAdapter(SQLSuppliers, Conn)
        DataAdapterSuppliers.Fill(DataSetSuppliers, "Suppliers")
        Conn.Close()


        txtcode.DataBindings.Clear()
        txtname.DataBindings.Clear()
        txtadd.DataBindings.Clear()
        txtregion.DataBindings.Clear()
        txttel.DataBindings.Clear()
        txtdate.DataBindings.Clear()
        txtemail.DataBindings.Clear()
        txttnumber.DataBindings.Clear()
        txtfnumber.DataBindings.Clear()

        txtcode.DataBindings.Add("Text", DataSetSuppliers, "suppliers.SN")
        txtname.DataBindings.Add("Text", DataSetSuppliers, "suppliers.Sname")
        txtadd.DataBindings.Add("Text", DataSetSuppliers, "suppliers.Address")
        txtregion.DataBindings.Add("Text", DataSetSuppliers, "suppliers.Region")
        txttel.DataBindings.Add("Text", DataSetSuppliers, "suppliers.Stel")
        txtdate.DataBindings.Add("Text", DataSetSuppliers, "suppliers.fDate")
        txtemail.DataBindings.Add("Text", DataSetSuppliers, "suppliers.email")
        txttnumber.DataBindings.Add("Text", DataSetSuppliers, "suppliers.Tno")
        txtfnumber.DataBindings.Add("Text", DataSetSuppliers, "suppliers.Fno")

Someone Help me please.

What I have tried:

I tried alot really but i Couldn't fix it because i'm not professional. :(

Posted 13-Oct-17 9:21am

Member 13464012

Updated 13-Oct-17 10:03am

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

OriginalGriff · Accepted Answer · 2017-10-13T10:03:00

Don't do it like that! Never concatenate strings to build a SQL command. It leaves you wide open to accidental or deliberate SQL Injection attack which can destroy your entire database. Use Parametrized queries instead.

When you concatenate strings, you cause problems because SQL receives commands like:

SQL

SELECT * FROM MyTable WHERE StreetAddress = 'Baker's Wood'

The quote the user added terminates the string as far as SQL is concerned and you get problems. But it could be worse. If I come along and type this instead: "x';DROP TABLE MyTable;--" Then SQL receives a very different command:

SQL

SELECT * FROM MyTable WHERE StreetAddress = 'x';DROP TABLE MyTable;--'

Which SQL sees as three separate commands:

SQL

SELECT * FROM MyTable WHERE StreetAddress = 'x';

A perfectly valid SELECT

SQL

DROP TABLE MyTable;

A perfectly valid "delete the table" command

SQL

--'

And everything else is a comment.
So it does: selects any matching rows, deletes the table from the DB, and ignores anything else.

So ALWAYS use parameterized queries! Or be prepared to restore your DB from backup frequently. You do take backups regularly, don't you?

So use the appropriate TryParse method to convert your text to a native datatype, and pass that to SQL via parameters.