From: esquel@sommarskog.se   
      
   M Joomun (m.a.joomun@qmul.ac.uk) writes:   
   > Thanks for the reply. As requested, below is the structure of the table   
   > in question. Not sure if you wanted everything the create statement put   
   > out, but shout if you do:   
   >   
   > CREATE TABLE [dbo].[tblAssay](   
   >      [AssayID] [int] IDENTITY(1,1) NOT NULL,   
   >      [ADtdate] [datetime] NULL,   
   >      [ADtTime] [datetime] NULL,   
   >      [LabNo] [nvarchar](6) NULL,   
   >      [AssayTy] [smallint] NULL,   
   >      [ReasonRepeat] [tinyint] NULL,   
   >      [DateAssRequested] [datetime] NULL,   
   >      [TimeAssRequested] [datetime] NULL,   
   >      [PersonReq] [smallint] NULL,   
   >      [RepeatedYN] [smallint] NULL,   
   >      [DateRepeated] [datetime] NULL,   
   >      [DtRepeatDy] [nvarchar](9) NULL,   
   >      [PersonRepeat] [smallint] NULL,   
   >      [ReasonNotRepeated] [smallint] NULL,   
   >      [LIMSUpdateYN] [smallint] NULL,   
   >      [DateAssayReq] [date] NULL,   
   >   CONSTRAINT [aaaaatblAssay_PK] PRIMARY KEY NONCLUSTERED   
      
   So far it looks good. But I think we need to see the whole picture.   
      
   So can you produce a script that includes:   
      
   1) Some INSERT statements.   
   2) The full code for the stored procedures.   
   3) Some calls to the stored procedure that demonstrates the problem?   
      
      
   --   
   Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se   
      
   Links for SQL Server Books Online:   
   SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx   
   SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)