July 7, 2004 at 2:31 am
My first guess is that someone added a password for sa. It's one of the vulnerabilities that was exploited by one of them dang worms, I can't remember if it was slammer or whatever.
The way I get my connection strings is to create a file with a .UDL extension. Then I open the properties and set up my connection. You can then open the file with Notepad(or other text editor) and copy out the connection string. If you can set up a UDL that works when testing, you've got other problems, then you can look at your code.
July 7, 2004 at 7:40 am
Thanks but I find found out were it stops it is the line
sSql = "Select * from futurecash Order by Rnum"
The problem seems to be the Order By Rnum. I can run it with out the order by. Do you know what the issue is with Order By?
Thanks
Paul
July 7, 2004 at 10:55 am
Try to incorporate your logic in the stored proc instead of running select/update statement on the front end.
It is also good for the speed and security reason.
July 7, 2004 at 1:16 pm
What kind of field is Rnum and does it actually exist in the table? ntext, text, or image columns cannot be used in an ORDER BY clause.
July 7, 2004 at 1:42 pm
The Rnum field is an INT.
July 7, 2004 at 2:11 pm
Put [] around the RNum. You need to list the columns instead of having * also. This is bad for performance and lazy coding. Also, as someone mentioned earlier, you need to be writing stored procedures for this and calling those instead of using inline code.
Derrick Leggett
Mean Old DBA
When life gives you a lemon, fire the DBA.
July 7, 2004 at 2:17 pm
Just a WAG on my part here but have you tried using the TOP keyword in your SELECT statement to see if that works?
|
Viewing 7 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply