Assuming you're talking the run-time version that's provided by the Office
Developer edition or Visual Studio Tools for Office, it's royalty-free, so
there shouldn't be any issue with licensing.
For the non run-time version, you must have a license for each user.

Signature
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)
> What are the licensing requirements for using a run-time version of an
> Access database on a Terminal Server?
> Is only one Access license required for the server installation? What are
> the license requirements for client access to the back-end data?
Michael Allen - 21 Dec 2004 12:49 GMT
Thanks Doug. Is there a licensing requirement for accessing the back end
data?
Mike
> Assuming you're talking the run-time version that's provided by the Office
> Developer edition or Visual Studio Tools for Office, it's royalty-free, so
[quoted text clipped - 7 lines]
>> are
>> the license requirements for client access to the back-end data?
Douglas J. Steele - 21 Dec 2004 14:01 GMT
I probably should have put this warning in my first response: I'm not an
expert on the legalities of licensing, so you may want to contact Microsoft
if you're really concerned.
My understanding is that realistically there are no licensing limitations on
using an MDB file to store data. The licensing restrictions are on running
Access so that you can use forms, reports, macros and modules: in other
words, on the front-end.

Signature
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)
> Thanks Doug. Is there a licensing requirement for accessing the back end
> data?
[quoted text clipped - 12 lines]
> >> are
> >> the license requirements for client access to the back-end data?