We could save a ton of Disk and, more importantly bandwidth/time, if Lotus were to implement Single Copy Template on the Client and support roaming using that technology. The files now are large - even when empty - to copy to a new PC in low bandwidth environments.
Subject: how would you implement this?
If a database has SCT enabled, it uses the centrally stored design of the database instead of having all design elements ‘on board’ itself. But if you create a local replica, the design gets replicated anyway. At least that’s how I understand it. How would you implement SCT, then? If the database does not reside on a server, how would it get its design? From a locally placed template?
Subject: RE: how would you implement this?
I think he’s concerned with the designs as they are stored on the server. When you activate roaming, you have, what… 3 or 4 databases per user replicated to the server environment? If those files were SCT-based, then the space savings would be even greater than they are for mail users. (4 NSFs x the design for each = around 8MB/user)