Forum Replies Created

Viewing 15 posts - 91 through 105 (of 217 total)

  • RE: Row Size is too large?

    ahhh...of course I get another error. After changing the varchar(8000) to a text type, I now get this error:

    select RGnameLast+', '+RGnameFirst AS Adjuster, RGnameLast, COcity AS ClientOffice, IOofficeName, WRworkOfficeId,...

  • RE: Row Size is too large?

    Thanks guys...it's just a bunch of text from an online diary. It does not contain any keys or any unique data like that. Just a bunch of text...

  • RE: Row Size is too large?

    Oh ok, so just change it to CONVERT(TEXT, WRnotes), right?

  • RE: Row Size is too large?

    Good point...but removing it still gives me the error.

  • RE: String or binary data would be truncated

    With the new SP, I am getting a

    Line 6, Incorrect syntax hear ','.

    But I don't see any misplaced commas....

  • RE: String or binary data would be truncated

    No, it's not too hard to copy it, but I just wanted to work on one thing at a time. But I will give it a shot right now...

  • RE: String or binary data would be truncated

    Forgot to include a script.

    Hey guys, I forgot to say that I am getting the above error in an update section of the script page. The update statement looks...

  • RE: String or binary data would be truncated

    Ok guys, I tried the CAST as text method and it is still giving me:

    String or binary data would be truncated.

    I haven't had a chance to trim down the SP...

  • RE: String or binary data would be truncated

    Yes, I am writing data to a temp table with this query using an ASP script:

    if exists (select * from INET.dbo.sysobjects where id = object_id(N'[INET].[dbo].[jones_temp]')

    and OBJECTPROPERTY(id, N'IsUserTable') = 1)...

  • RE: String or binary data would be truncated

    I'm using a temp table and I need the cursor. I guess I could try it without as soon as I fix this other bug.

    Anyway, "Results" is not large...

  • RE: String or binary data would be truncated

    I tried doing SUBSTRING(Results, 0, 7999) AS Results1, SUBSTRING(Results, 8000, 15999) AS Results2

    but that did not work...

  • RE: Date issue in Query

    Awesome...both ways work.   I tried KH's way and Pam's way of using:

    BETWEEN '2006-05-01 00:00:00.000' AND '2006-05-01 23:59:59.000'

     

    Thanks Guys!

  • RE: Date issue in Query

    I just checked, and DEenteredDate does have time, like this:

    2006-03-15 11:13:57.000

    so should my search be BETWEEN '2006-05-01 00:00:00.000' AND '2006-05-01 11:59:59.000' ?

     

     

  • RE: Date issue in Query

    Pam,

    That does work, but shouldn't BETWEEN '2006-05-01  00:00:00.000' AND '2006-05-01  00:00:00.000' find all results with a PayDay(DEenteredDate) of 5/1/2006?

     

    Thanks!

     

  • RE: Date issue in Query

    SQLBill, 

    Thank you for your suggestions.  I tried using:

    BETWEEN '2006-05-01  00:00:00.000' AND '2006-05-01  00:00:00.000'

    But still no results were returned.  I am not sure what the heck is going...

Viewing 15 posts - 91 through 105 (of 217 total)