Hi All,

I am hoping someone may be able to clarify why the .sql file created by the Publish to Provider application in VS2010 keeps getting rejected by my web host import routine.

To explain, I needed to create the ASPNETDB database on my web host and as you would expect, I used the Publish to Provider utility in VS2010 to create a .sql script to accomplish this.

As mentioned, this always got rejected so I began by taking each T-SQL statement to identify which statement was failing and transferred them to a manually created text file called "manual.sql". After each import test to my host it was successful??

The culmination of my trail and error routines ended up with a manually created file which was exactly the same as the originally created file from the Publish to Provider utility which then imported successfully????

The question is why did the original file from the Publish to Provider utility not work?

The only thing that stands out as a giveaway to the potential error is the difference in the file size of the two files. The manual file that I have ended up with, which imports fine, is exactly (within 3 bytes) half the size of the originally created file?

As you can see I have got round this issue but it would be great to find out what the source of the problem was so that it could potentially be solved at the creation of the original file from the Publish to Provider utility.

Sorry, I was hoping to upload the two files for reference but it seems I cannot do this.

Thanks in advance to anyone who may be able to help.

Kind regards,

Ian Ryder.