Thanks again James for your assistance. I've cracked it though. Unfortunately the error messages I was receiving weren't providing enough clues (for me) to find the root of the problem easily enough but fortunately the solution was very simple to implement once I had an idea of the problem.

I started a new project and pieced it together bit by bit using the files from my previous project (the one giving the errors) just until I started to receive my first error, which was...

"Failed to generate a user instance of SQL Server due to failure in retrieving the user's local

application data path. Please make sure the user has a local user profile on the computer. The

connection will be closed."

This occured when my localisation code was added (as expected)

I googled this error and found out the problem relates to the SQL Express instance that was being automatically generated, as well as the local user name on the server.

Then I read a post at http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=125227&SiteID=1  by a member that cracked it on the head for me. I didn't follow his instructions completely since my set up was different than his but I used the suggested aspnet_regsql utility to register my existing sql server 2005 db to be used by the profile provider and VOILA!! the errors disappeared.

Also I added to web.config file :
<remove name="LocalSqlServer"/>
  <add name="LocalSqlServer" connectionString="data source=xxx.xxx.xxx.xxx\sqlexpress;Initial Catalog=myDB;User ID=user;Password=pass"/>

Deakus.