Double-check the report definition and make sure that it is really printing "Date1" as you expect. Another thing to do is confirm that the cursor is correct by putting a BROWSE in the code just after you do the massive SQL SELECT. It may be that the cursor is correct but you are accidentally printing the wrong field.

Cathy


>Hi Cathy:
>
>Your idea worked. Thank you.
>
>Here is one part of the code where i am getting the wrong date.
>
>

UNION ALL SELECT '6' AS SortKey, 'Consultations' AS Group, ;
>    '' AS Extra1, '' AS Extra2, '' AS Extra3, ;
>    '' as Extra4, '' as Extra5, '' as Extra6,;
>    0 as Extra7, '' as Extra8, '' as Extra9,;
>    '' as Extra10, CReference as Extra11,;
>    Daterefer AS Date1, {} AS Date2, {} as Date3, {} as Date4,;
>    HealthNum, Specialist AS Descr FROM Consultants;

>
>The field DateRefer has the correct date stored in the Consultants Table. However, when I set DateRefer as Date 1 ( as shown above), I get a different date (7/1/1972 instead of 7/20/2003) in the TmpData cursor. Incidently 7/1/1972 happens to be the BirthDate of the patient, but 7/20/2003 is the date stored in the Consultants.DateRefer field.
>
>Thanks Cathy.