I had previously added to this thread good point   Still is a good point,

but rather than following the way of expressing the date as given

in the article (mm/dd/yyyy) which is ambiguous for those of us outside the

USA, you should follow the example given in trusty books online

This example restores a database to its state as of 10:00 A.M. on July 1, 1998,

and illustrates a restore operation involving multiple logs and multiple backup devices.

-- Restore the database backup.
RESTORE DATABASE MyNwind
FROM MyNwind_1, MyNwind_2
WITH NORECOVERY
GO
RESTORE LOG MyNwind
FROM MyNwind_log1
WITH RECOVERY, STOPAT = 'Jul 1, 1998 10:00 AM'
GO
RESTORE LOG MyNwind   
FROM MyNwind_log2   
WITH RECOVERY, STOPAT = 'Jul 1, 1998 10:00 AM'
GO

This example shows that you can express the date in a less ambiguous format.  
I imagine (though I haven't tried it) that the widely accepted format 
of yyyy-mm-dd hh:nn where hh is 24-hrs would also work.