Windows 7 Professional Access and Terminal Service

A question came in today from Michael about terminal services scale: I have been using the Access 2003 runtime in conjunction with the sagekey scripts for a couple of years. My deployments have had pretty light concurrent user counts,Windows 7 Professional, 10-20 is typical. I have a client that would need it to scale to at least 100 concurrent users, possible 200-300. I know the scalability of an app would be impacted by what the front end is doing and so forth. The hardware side can be whatever it needs to be, so I'd assume that part of the equation will be ok. The backend is sql server and I'm sure it can handle the load fine. I use a mix of linked tables with plain Access queries against them, and stored procedures in sql server invoked via pass-through queries. Access to the app is provided via Terminal Services with a helping hand from Citrix PM. In the system I use, each user gets their own copy of the Access front end. Thus, as far as the scalability concern goes, the concern I have is that the terminal services box which hosts the Access front ends will be running many copies of Access and/or the application in memory. I just don't know enough about the way Access and Windows and TS work together to know how that all plays out. It's not so simple to set up a test bed for this... But maybe I'll need to do that. I was hoping that you might have some insight into this issue since you have inside exposure to Access and a good tap into the community of Access developers? What are the largest concurrent user counts that you've heard of? Any input is appreciated. Anyone from the community have experiences you would like to share with Michael? <div