short of writing your own VBA procedure to import the data I cant' think of a way.
if you find you are going to be importing a great deal of spreadsheets then a VBA procedure may be 'the' way forward. you could validate data, make certain its 'sane' Ie within reasonable / expected limits. decide what to do on finding data errors (ie do you reject the whole spreadhsheet and make the submitter re -edit till it does clear, do you import what you can, shift rows with errors into another table(s) within Access and let the users clear faults there.
A bit of crafty design means your VBA procedure could run overnight or as a background process, meaning the most recent data is always incorporated.
Personally I always caution people using spreadsheets as an original for data. they are great at consuming and manipulating data, incredibly powerful and flexible, but that is also part of their down fall. its all to easy to make an inadvertent change to a spreadsheet (add or delete a column/row without realising the impact of those changes. if you import into Access using the macros/wizards then there is a risk that the datatypes can get mangled. its fine if you use a spreadsheet type file as an interface file between different computer systems and you cannot get a direct feed from the host system, but as the source for raw data... be very very carefull
I'd rather be riding on the Tiger 800 or the Norton