you can use the upsizing wizard; but if i were you.. i'd talk in
general about what types of queries you use.. you'll probably need to
rewrite some of them

Since SQL Server and Jet Engine are different database system, when move
database in *.mdb file to SQL Server, some changes are inevitable, event the
move is merely on the BE.

You can move tables in *.mdb BE to SQL Server witj MS Access's "Upsizing
Wizard" fairly easy. But after upsizing, you still need to go through each
table's structure to verify each column's data type, index, primary key....
I remembered (could be wrong) the primary key may not be transferred, and
you need to re-specify primary key for each table. Also, the upsizing wizard
convert "Memo" column type in JET into "Text" or "NText", you may want to
change it to "vachar" or "nvarchar", since this data type in SQL Server can
le as long as 8K. Anyway, after transferring tables, carefully go through
the tables' structure, relationships, and do changes if necessary.

As for FE, you can still minimize the changes if your FE designed well (you
link the FE to SQL Server BE via ODBC). It is very hard to say how much
changes you need without seeing it, it could be minor, or major. One problem
with this FE is it is difficult to fully use SQL Server's power (SP,
UDF,...), many queries have to be processed in FE.

In order to fully use SQL Server's power in MS Access, you may re-design
your FE in MS Access *.adp project. Howerver, if the SQL Server is planning
to move SQL Server2005 soon, then MS Access ADP's future is still not clear
at this time.