Thought others might benefit from Mary Chipman's comments (from newsgroup):

An mdb is a better choice since you also have the flexibility of

storing static data locally in Jet tables, allowing you to decrease

round trips across the network to fetch data that rarely changes.

You can't update the results of a pass-through query, and that is the

only way to populate a form from a stored procedure in an mdb.

however, you can create unbound forms, populating the controls

manually and performing any updates in code by passing parameter

values to stored procedures. This involves writing a fair amount of

code, which you may not want to do.

If your main concern is network traffic, you can achieve a good result

by not binding editable forms to entire tables and still have bound

forms without the hassle of an unbound app. Create a "query by form"

interface that forces uses to only load a record at a time and set the

form's recordsource property to load the record with a WHERE clause

that only loads a single row (and its related rows in a subform) for

editing. Base browse forms, combo boxes,  and reports on stored

procedures called through pass-through queries. Perform all

aggregations in stored procedures, and any formatting or presentation

code in Access.

-- Mary

Microsoft Access Developer's Guide to SQL Server

http://www.amazon.com/exec/obidos/ASIN/0672319446