C# VS 2005 - SQL Query Parameters to an ODBC DataSource

[jcrcarmo]

Hello everyone,

 

I used to have my MS Access 2002 DataBase placed in my application folder and connect to it through an OLEDB connection. Everything worked fine.

 

Now I decided to create an ODBC DataSource and suddenly I'm not able to pass parameters to the SQL Query the way I used to with the OLEDB connection.

 

Here's a sample code of the SQL Query and C# code on my form:

 

FillByClienteDataNumero query:

 

SELECT Data, Cliente, Tipo, Número, Espécie, Lote, Análise, Preço 
FROM qryALL1 
WHERE (Cliente = ?) AND (Data >= ?) AND (Data <= ?) AND (Tipo = ?) 
ORDER BY Data, Número 

 

Form code:

 

private void btnSeekBA_Click(object sender, EventArgs e) 
{ 
try 
{ 
this.qryALL1TableAdapter.FillByClienteDataTipo(this.sascrDataSet.qryALL1, cbCliente.Text, new System.Nullable<System.DateTime>(((System.DateTime)(System.Convert.ChangeType(DataIni.Text, typeof(System.DateTime))))), new System.Nullable<System.DateTime>(((System.DateTime)(System.Convert.ChangeType(DataFin.Text, typeof(System.DateTime))))), "Boletim"); 
} 
catch (System.Exception ex) 
{ 
System.Windows.Forms.MessageBox.Show(ex.Message); 
} 
} 

 

Any ideas why the above SQL query and code work with an OLEDB connection but not with an ODBC DataSource? Thanks a million!

 

JC.

[PlausiblyDamp]

Does either version work if you simplify the parameters?

i.e. instead of

this.qryALL1TableAdapter.FillByClienteDataTipo(this.sascrDataSet.qryALL1, cbCliente.Text, new System.Nullable(((System.DateTime)(System.Convert.ChangeType(DataIni.Text, typeof(System.DateTime))))), new System.Nullable(((System.DateTime)(System.Convert.ChangeType(DataFin.Text, typeof(System.DateTime))))), "Boletim"); 

try

this.qryALL1TableAdapter.FillByClienteDataTipo(this.sascrDataSet.qryALL1, cbCliente.Text, System.DateTime.Parse(DataIni.Text), System.DateTime.Parse(DataFin.Text), "Boletim"); 

[teixeira]

Hi dear Portuguese friend,

 

As this is a forum, and here you discuss things, we suggest ideas, and we take out dought sharing the knowlegde and the experience of each one, I wanna suggest that using accented word as (à,é,ç,etc...)as fields names its not very good idea and you can get some incompatibilities with it.

And i wanna also sugest that using ODBC connection even its more standard and easy to use, it is slowest that OLEDB connection. And it is one more "tier" you are using in your application, who knows you related problem is related with the accent word you use as table fields in you ODBC connection.

 

.eof

 

Teixeira