On Fri, 11 Apr 2008 06:16:06 -0700 (PDT), DanWeaver wrote:
>
>> MySQL is an RDBMS. It implements SQL.
>>
>> What you are asking about has nothing to do with MySQL per se. It is
>> like suggesting that the makers of nuts and bolts should document how
>> to use them to build a car!
>
> Haha. Quite funny. But it isnt quite like that: it is like wishing
> that a kit-car manufacturers, or some enthusiasts
> placed their experiences of where to get the right oil in a public
> place to encourage others to have a go and not buy a normal one from
> the shop (ie SQLserver)! Hehe.
>
> I believe a few steps are necessary and Im not sure of the order or
> exactly how to go about them:
>
> A) Create the DB schema on a (shared host) MySQL db... Does anybody
> have the SQL already made?
>
> B) Set up the asp project to have a reference to the correct provider
> ie do something in web.config relating to <providers> and <connection
> string>...
>
> C) Change the ASP.NET Web Site Administration Tool to 'know' that
> we're now using a remote provider...
>
> D) Any other mystical steps involving importing namespaces etc...
>
> Any takers?

So, you're basically asking us to do you your project for you. Great.
I'll tell you the same thing I tell coworkers that want things done that
I don't want to do. I'll handle step A, and it'll be done two days after
I get a complete set of requirements, exactly as documented in those
requirements.

--
71. If I decide to test a lieutenant's loyalty and see if he/she should be
made a trusted lieutenant, I will have a crack squad of marksmen standing
by in case the answer is no.
--Peter Anspach's list of things to do as an Evil Overlord