Unanswered: Need another pair of eyes sql 'Order by'
my page suddenly stopped working when I wasn't working on it and it seems to be down to the 'ORDER BY' part of my SQL. I'm here alone as usual and I need someone to glance at the sql strings below. (yes, I do need the select *)
If I run this in SQL Manager it works fine:
SELECT * from dest_search WHERE trip_type like 'Trekking' ORDER BY start_date
if I do the same from my asp page it fails but if I leave out 'ORDER BY start_date' it works.
the error I get is:
Microsoft OLE DB Provider for SQL Server error '80040e21'
Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.
/Newindex/trip_types.asp, line 53
line 53 is the 'desc = oRS...' bizarrely
oRS.Open strSQL, oConn, 2, 3
Do while not oRS.eof
country = oRS("country")
53---> desc = oRS("description")
url_link = oRS("url_link")
startDate = oRS("start_date")
endDate = oRS("end_date")
trip = oRS("trip_type")
difficulty = oRS("difficulty")
not all the descriptions are filled in (some are null) but that doesn't stop SQL manager from working or unordered results coming up fine in my web page.
people can change TREKKING and that bit works, but I have simplified the sql string in this thread so people concentrate on what's going wrong.
the examples above work fine on the web page and SQL manager but the web version fails if I add 'ORDER BY start_date'
The fact that it all works fine makes me think there's no problem with spelling.
What's T-SQL and is that relevent to me using MS SQL Server and asp -vvbscript?
I removed the cursors and it works. thanks MCrowley
innitially they were 2,3 (whatever that means)
then I changed them to 0,1 and it worked then I removed them thinking that if I don't know what I'm doing I should go with the defaults... or change jobs.