Cheers Joepas,
I eventually overcame the problem. I in the end used SQL server but was forced to re-write all my SQL into my actual application logic in asp.net. As it turned out writing direct into the applcation logic was much better than using stored procedures.
Unfortunately my server company whom I am contractually bound with until god knows when do run SQL server and accept asp.net, but only accept .mdb rather than .adp, which is odd. I have overcome this problem and performance wise, it is running much smoother with a .mdb and application level SQL. I just had to remember to establish a configuration level SQL connection to my datasource so I didn't have to re-write it to every web page I created.
Cheers for your reply. Are you too an asp.net developer?
R