Thanks, does your table have a primary key?

You will need to post some more information for a complete solution.

Post your table ddls and some sample data and i am sure someone will be able to help

If jobNumber is a var char then this code will not work at all

SELECT * FROM vw_Job_Invoices_And_Credits WHERE JobNumber = 503875

You will need to add quotes to the Jobnumber

SELECT *...

I have to ask,

have you checked the SQL log?

The problem is that your are trying to convert a string that has a commas in it these are non-numeric characters and will not be able to covert into...

You can get this information from the Schema Changes report that is part of the default trace on sql 2005.

Right click on the db in SSMS --> Reports.

Or else...

Am not sure what you mean by 'get rid off' but if you want to count just the numbers then use this

select len( replace('123-45-678','-','') )

No Worries , Thanks for the feedback..

try using row_number()

;WITH SchoolOrder AS

(SELECT id,class,name,avaliation,

ROW_NUMBER() OVER (PARTITION BY class ORDER BY avaliation DESC) AS TheOrder

FROM school

)

SELECT * FROM schoolorder WHERE theorder <4

perrydwill (10/16/2008)

---

Oh crap. After looking at the table more closely the format isn't consistent. I have some that have their whole middle name instead of initial, some that...

I ahve to agree with Luke's comments, it is apparent that all your names do not follow the same format. You could try

SELECT Fullname,

...

perrydwill (10/16/2008)

---

Thanks to you both for you responses. It appears that both resolutions would require me to manually type in each name within the script to reformat them. ...

If the data is consistent across all the names, then this code will be able to split the names, I tested it against the small sample provided and it works....

You can do this in SQL ,

Post up some sample data and the query that you wrote and I am sure that some one will be able to help you

morten (10/15/2008)

---

Hi

Thanks. I will have a look at that.

Does that mean that we have a potential bad code in our CMS to allow sql injections? or would it more be...