Do you have to have MS Sql Server installed to use these commands? The
machine I am programming on is also set to develop PHP/MySQL and is running
Apache. Hence, I did not install MS Sql Server when installing VS 2005.
The following is not available to me while programming:
using cmd as SqlClient.SqlCommand("SELECT * FROM MYDATES WHERE ((theDate)
BETWEEN @Start AND @End)",dbConnection)
SqlCommand is an invalid property and when I search MSDN it is referenced to
SQL Server.
I think I am just a newbie - but cannot imagine that there is not a simple
equivalent to the way we used to just pass a SQL statement to a Data Control
and refresh!! I was always able to create end user generated queries on the
fly. (Enough wining)
Thanks,
Ross
"phonl" <ph***@newsgroups.nospamwrote in message
news:eF**************@TK2MSFTNGP05.phx.gbl...
Try using ".FilterExpression" and see if it will work for you.
ado2.net is much more complicated than the ado we were using. Some vb6
programmers think it is hard to learn the vb.net language. I have found
that it is easy compared to ado2.net. Why they even call it ado any
longer is strange. ado2.net is for web programmers who use disconnected
data.
"Ross Contino" <ro*********@comcast.netwrote in message
news:fY******************************@suscom.com.. .
>Howdy:
I am an experienced VB 6.0 database programmer trying to write first VS
2005
application in VB 2005. I want to create an end user defined query and
pass
it to the program. Specifically, I want to pass a date range, ie:
SELECT * FROM MYDATES WHERE ((theDate) Between #8/1/2006# And
#8/7/2006#);
However, the user wants to enter the date range on his own. In the past
I
would generate the SQL on the fly and pass it to a datacontrol as the
datasource. Now it seems Queries are made with the Query Builder and
stored
in "WhateverDataSet.xsd" file.
How do I retrieve the current "Text" that defineds the query at runtime,
change it, and refresh it to display a new date range?
Eventually, I want to pass this same range to a report. Is that
possible?
Thanks,
Ross