Sounds to me like your developers are the ones who are confused. Both Access and SQL Server datetime fields store both the date and time, whether you enter both, or not. So, your query is working correctly. (Given a choice between a query and an Enterprise Mangler (EM) display, always go with the query results. EM lies.)
I’d say your dev guys added two datetime fields to their Access table and formatted one for date and the other for time. The wizard apparently noted this and somehow passed the info on to EM. But, what is actually stored is what MS calls a “dateserial” that contains all date AND time info. It will store default values, if none are provided for one or the other. I’d bet the field that is only supposed to have dates in it has midnight as the time for every record, for example.
This is assuming the developers didn’t do something as totally amateur as using text fields to hold the dates and times. I suppose it’s possible the upsizing wizard could convert those into datetime fields, if you told it to. Again, each column would have the same value, for each record, for the part not provided by the developers.
Tell them to open their base table directly, in design view, and verify the data type of these fields. If it’s Date, have them remove all formatting from those fields, and then have them view the datasheet, still in the base table. They’ll see what you’re seeing in your query.