You are right: the ContinueDestinationPageUrl attribute of the CreateUserWizard is, indeed, used in the sample we supplied in the kit.  I was incorrect when I said that it is not supported.  I looked again and recall now that we found that this attribute is recognized and honored by the framework regardless of whether an adapter is applied.  So it works with and without adapters... at least, that's what Heidi and I seemed to find when we built the sample page to demo the adaption of the CreateUserWizard control.

I'd like to return to your original problem and see if I can duplicate it here.  What exactly do I need to do to make this happen on my PC?  Clearly I can't simply run the sample page from the kit.  It is configured with a "fake" membership provider.  What exactly do I need to do to recreate the problem you are seeing?  If you can describe that I'll spend the time here to follow your recipe and then do some debugging to try to help you overcome the problem.  OK?  But first I need the recipe.  You said that you'd provided the steps above but I've reread this thread several times and I don't understand exactly what I need to do yet.  Can you walk me throught it a bit more verbosely?

Cheers.