I'd like to deploy an Access 2000 classic "split" db at a site that has
need to access the db via the LAN in the usual fashion, and also have
some remote users using the db via Terminal Services (win2003 server).
I'm not 100% what the ideal setup will be. Terminal Services will be
running on a new dedicated server; and server that currently hosts the
backend will remain. The regular LAN users will still work with a local
copy of the front end, linked to the backend mdb (on one or the other
servers).

I'm not all that used to Terminal Services. I think the standard setup
will be to create a folder for each remote user on the TS machine. Then
deploy a runtime version of the Access front end into each folder to
make the licensing work (it's possible that all the remote users will
have copies of Access, so maybe runtime wouldn't be required).

Now, I guess it's self evident that the backend could be on either
server...the only thing I'm not sure about is permissions. I know TS
servers have to be configured with particular permissions; is it safe to
assume the users coming in to the LAN via the TS would be able to relink
to the Access backend on the other LAN server, if I did place the
backend there? Kind of think those perms would be ok, ie not contrary to
TS sec needs, but don't want to assume anything.