A lot of! These connection strings can't work, but I need more information to help you.

First question - how did you setup a database for the sql server running at ip 209.200.235.3?

You need to setup an empty database first on that server, define security permissions, etc. Did you take these steps?

Ok.

SQL Server 2005 will not load an database by its file name - this is a special feature of SQL Server 2005 Express. If your provider has only SQL Server 2005, you will need to attach the files as a new database to that instance, setup security again and finally use the classic connection string like you have done using msde or sql 2000.

I have been the one who kindly informed you before. There are different syntaxes of connection strings for sql server.

1) Server=.\SQLExpress;AttachDbFilename=pathtofile\database.mdf;Database=dbname;Database=dbname;Trusted_Connection=Yes;"
This string is used to attach a database file to a local SQL Server Express instance.

2) Server=servername\serverinstance;Database=DNN;User ID=xx;Password=xxxx;Trusted_Connection=False
Connects to the database DNN on the server servername, instance serverinstance using sql server security
This is aquivalent to
Data Source= servername\serverinstance;Initial Catalog=DNN;User Id=xx;Password=xxxx;
You are able to replace the servername with the IP address

3) Server= servername\serverinstance;Database=dnn;Trusted_Connection=True;
Now the owner of the running dnn process needs to have the permission to access the database using windows authentification. Ip address will not work!

There are some more possibilities, for more information see http://www.connectionstrings.com/

The main information for you:
Sql Server 2005 Express has to be installed on your local server if you want to use variant 1). Otherwise there is no difference between sql 2000, sql 2005 or sql 2005 express