It took a lot of hacking, but I can sum it up fairly easy by following these steps (which I mostly got from the CrystalTech forums and Google):

• Test and make sure your Starter Kit works properly on your local machine.  This will help us with troubleshooting later.
• Configure ASP.NET 2.0 Application Services to use SQL Server 2000 or SQL Server 2005 (perfect blog with detailed instructions at http://weblogs.asp.net/scottgu/archive/2005/08/25/423703.aspx).   Make sure to run this against your newly set up SQL 2005 database, as this step replaces the database (ASPNETDB.MDF) that came with your Starter Kit.  Technically it doesn't replace your database, but SQL Server 2000 is referenced instead.  NOTE:  this will place ~20M data into your new database (not good for those of us on the developer plans with small amounts of available server space).
• Make sure to use MorningZ's suggestion and create the necessary Personal Web Starter Kit tables in your database (http://www.microsoft.com/downloads/details.aspx?FamilyId=2EE85ED4-7613-47E2-8375-17222B150E4F&displaylang=en).  This is the same thing as the database your Starter Kit came with (Personal.MDF).
• Make some changes in the web.config to accomodate the new database settings.  I made the following changes, but can't promise that it will work the same for you:
  <connectionStrings>
    <add name="Personal" connectionString="Server=[servername];Database=[Database name];User ID=[UserID];Password=[Password];Trusted_Connection=False" />
    <remove name="LocalSqlServer"/>
    <add name="LocalSqlServer" connectionString="Server=[servername];Database=[Database name];User ID=[UserID];Password=[Password];Trusted_Connection=False" />
  </connectionStrings>
  Make sure to replace the brackets and names with values specific to your account; i.e., [servername] for me is SQLB1.webcontrolcenter.com.  Replace [UserID] with your user id, [Password] with your password, and so on.  Yes, it's secure ...
• And I don't know if I had to do this, but did because I read I was supposed to.  I added a <membership> section to the <system.web> section, right underneath </authorization>.
  <membership defaultProvider="SqlProvider" userIsOnlineTimeWindow="15">
    <providers>
    <clear />
    <add
      name="SqlProvider"
      type="System.Web.Security.SqlMembershipProvider"
      connectionStringName="[connection string name]"
      applicationName="[application name]"
      enablePasswordRetrieval="false"
      enablePasswordReset="true"
      requiresQuestionAndAnswer="true"
      requiresUniqueEmail="true"
      passwordFormat="Hashed" />
    </providers>
  </membership>
  
  For <connectionstringname> I used LocalSqlServer from above.  Just type in "LocalSqlServer".
• Publish your *working* Starter Kit (from Visual Studio, Build then Publish) - i.e., it's been tested and runs on your local machine - to your CrystalTech IP address and subdirectory (if applicable).


I'm still making tweaks and have come across miscellaneous errors, like directory not found (just create a new one) and stored procedure not found (just republish the solution) ... but at least it's working!Good luck ... and have fun!
Brent
http://www.solvix.com/portal (working site)

I did create all the tables and stored proc's on sql 2000. How can I populate my new tables with Personal.mdf data, so I can run my starter kit.

Thank You.