Yes, one user that opens the 2 reduced documents will use 2 document CALs. If a user uses more than 4 document CALs it is better that they have 1 named CAL. Beefing up hardware would probably be cheaper, you'll be able to load bigger QVWs and I like keeping as much information in one model as possible. However, as the application grows so will the response time, and when the response time becomes unacceptable, I think this is the best time to start dividing the files into separate QVWs. I would analyze the response times with the user and the impact the data volume has on that response time. Along with that measure and the speed at which the data volume is growing will help you decide if beef up the hardware or break down the QVW.