No Result set with a WHERE Clause.

  • What happens when you explicitely CAST your date as DATETIMES?

    Or when you write WHERE... >= '20041214'....?

    --
    Frank Kalis
    Microsoft SQL Server MVP
    Webmaster: http://www.insidesql.org/blogs
    My blog: http://www.insidesql.org/blogs/frankkalis/[/url]

  • Put SET DATEFORMAT YMD at the beginning of your procedure

  • Even better is to use a language independant format.

    Here are some very good thoughts by SQL Server MVP Tibor Karaszi on this topic: http://www.karaszi.com/sqlserver/info_datetime.asp

    --
    Frank Kalis
    Microsoft SQL Server MVP
    Webmaster: http://www.insidesql.org/blogs
    My blog: http://www.insidesql.org/blogs/frankkalis/[/url]

  • I'm not sure what you mean by "What happens when you explicitely CAST your date as DATETIMES?" The B.TimeStampEntered Column is already a DATETIME DatType. Here is a sample for this column, 2001-07-04 14:15:39.633

    And the SET DATEFORMAT to YMD did not achieve anyting either.

    This has really blown me away. There must be something else werong but don't know where to look.


    Kindest Regards,

  • I have sorted out this issue. It was a data quality problem between the UserEntered column and the LanUserId column ob the JOIN.

    Thanks to all for your help.


    Kindest Regards,

Viewing 5 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply