It would seem that the logical way to set up SF in a team environment would be to use a common SF database so that multiple developers cold work on the same project. It would be nice if the installation process we're smart enough to realize that the SF and Sample databases were already updated to the current level. In our environment the SQL database is located across a WAN making each install a 30+ minute process while the demo data is loaded.

While installing StrataFrame the installation process encountered an error while trying to deploy the StrataFrame metadata. This may be due to the fact that an install was running on another PC. Should the install process handle concurrency when there are multiple installs running that share the same SF and sample database?

When StrataFrame is installed should it be useable by anyone that logs on to the PC or only to the user that installed it? After installing SF successfully under one user ID the StrataFrame menu was not visible to another user that logged in to the same PC. The templates were there but the SF menu in Visual Studio was missing.

-Larry