Cynthia has given you some excellent advice regarding handling this data. I am going to point you to a couple of other aspects, and hope you will get a full resolution from Tech Support.
The value '01Apr2008'd is a date literal that has a value in SAS internal storage of 17623. This is the number of days since 1Jan1960 as Cynthia explained. The value '04:53:43't has the same internal storage value, and is the number of seconds past midnight. You could have established this with a simple data step to check the values and apply date and time formats. That is the first lesson in debugging unexpected values. Note that the formats don't change the underlying values, they only change the way in which the values are represented. So your statement that the date is reported as Date7 is an artefact of the default format on the table, and is both irrelevant to the actual value of the data, and is something you can change.
What this also instructs us is that the internal value is not being changed in the load to SQL Server, but is being represented incorrectly. This is an important finding since it shows us that we have a data representation issue, not a data corruption issue. As to how to correct the load; I cannot advise you. I don't have Access to SQLServer or ODBC here to test any solution, and this is the sort of problem that needs testing. As Cynthia said, Tech Support is your best bet.
I will comment though that Access, Excel and SQLServer all store datetimes in the same way. The integer part represents the number of days since 1900, so if the values have not suddenly shifted off by 60 years then the load process has recognised the change in the epoch used by the two different systems. That is good news. To hold a time of day, the MS products use decimal parts of days, where 6am is 0.25.
So if your value is going in as a datetime, and coming back as a date or time, then you have a problem in the way in which the data type is represented. I am sure Tech Support will give you clear indications where that is going wrong. I suspect too that careful reading of the manual, or researching of the user papers on support.sas.com would also shed some light.
Kind regards
David