[smirkley]

Well thanks Lynne. Sincerely.

But instead of messing it all up with three different sites and special code,... what I was suggesting is to have the Legacy site where it is at, and start building the new site on root.

VB org is on what 3.6?,,,.. and vB com is getting ready to roll out v5 when it goes gold?... and someday likely 3 or so years,... we will have vB6. etc.

I know BirdOPrey5 can only handle one site to moderate, and I wouldnt expect more than that of anyone here as I know it is work.

And since it is just too much to handle to migrate the current vB org over to 5,..

Why not just make a vB5 instance on the root.

Leaves me with the question of just how long vB org will be supporting legacy products prior to 5. And if they do or dont, how long is vB org going to be running on legacy software but yet representing the new stuff?

Seriously, I really dont care myself. I will always come to vB org for quality third party extensions for my website whether on 3, 4, or 5, or whatever.

My suggestion was only for image and marketing reasons in regards to the vB conglomerate of sites.

Thanks for letting me offer my feedback, as it is.

-Mark-