Aravind, try this solution and see if it does the trick for you

SELECT     a.ID,

           MAX(CASE WHEN b.Col2 = 'X' THEN b.Col1 END) X,

           MAX(CASE WHEN b.Col2 = 'Y' THEN...

Also you consider changing your database engine from DAO to ADO in ACCESS 2003 when upgrading a solution from ACCESS 97.

Yes, that is because SQL Server automatically has a RETURN_VALUE output, shich you need to catch.

You can do without DTS. You can use OPENROWSET instead.

Use CHARINDEX function.

SELECT Calldata, CHARINDEX('/', Calldata) FROM [Ron's Table]

Call with either.

SELECT           Priority,

                 MIN(dbo.fnMEDIAN(NULL, Priority, 2)) Median,

                 COUNT(*) Count

FROM             MyTable

GROUP BY         Priority

ORDER BY         Priority

Or

SELECT           Priority,

                 MIN(dbo.fnMEDIAN(NULL, Priority, 3)) Median,

                 COUNT(*)...

Yes. Replace the MEDIAN function with this new one. For getting the median over Priority only, call this function with dbo.fnMEDIAN(NULL, Priority, 2) or dbo.fnMEDIAN(NULL, Priority,

Dinakar has a solution, but the way he wrote it, the database can't use any index for the date column.

Use this instead

SELECT * FROM my_table where created_date >=...

SELECT           [Type of Request],

                 Priority,

                 MIN(dbo.fnMEDIAN([Type of Request], Priority, 0)) Median,

                 COUNT(*) Count

FROM             MyTable

GROUP BY         [Type of Request],

                 Priority

ORDER BY         [Type of Request],

                 Priority

Or

SELECT          ...

David, you are aware the BETWEEN operator is INCLUSIVE with limits?

In your case, BETWEEN 7 AND 15 is true for hours 07, 08, 09, 10, 11, 12, 13, 14 and...

You mean something like this? I took the liberty to rewrite and optimize your procedure a little...

ALTER PROCEDURE dbo.p_dtu_Store_Line_Fault_Data

(

    @AssetID int,

    @Timestamp datetime,

    @FaultCode int,

    @State int

)

AS

N 56°04'39.16"
E 12°55'05.25"