Not sure. Could you do something like

osql /L > sqlservers.txt

to redirect the output to a file called sqlservers.txt and then use that in your app?

SQL 200 - that must have been a while ago

Have you tried installing EM on another PC and seeing whether it happens there...

What is your question?

Creating and deleting tables uses resources, of course, and this is an unusual way of designing an application.

Whether this starts to cause you performance problems depends on volumes, hardware, how...

Well, I guess you could try this.

First off, replace all of the single quotes with something else - eg ~ or some other character that does not exist elsewhere in...

The single quotes will cause all sorts of problems, that's for sure! If you already have an ASP page that does (or should do) this, it will probably handle the...

Ace.

What's the datatype of the content field?

It's best if you specify the fields that you are INSERTing into - also use single quotes and dump the curly brackets:

INSERT INTO FamousFacesSubmissions (StoryID, SubscriberID, DateSubmitted)

VALUES (newid()

OK, I know what this is. The ID will have a data type of 'uniqueidentifier', probably with a default value of newid(). SQL Server will generate this for you on...

So the question is: "What generates the SubmissionID code?"

If it's a SQL Server IDENTITY field, you can try the INSERT statement I gave you, but without the SubmissionID, ie

Try inserting the row without the CONTENT and SELECTED fields first. If it works, we'll move on to CONTENT.

INSERT INTO mytable (SubmissionID, StoryID, SubscriberID, DateSubmitted)

VALUES (p1, p2 ,p3 ,GetDate())

and...

The very existence of an 'insert row' option makes it difficult to suggest that this is 'wrong'

You are using tools that I have...

No problem. Regarding the syntax / access violation problem, can you post the SQL command that you issued?

OK - don't do it, you are right!! It will not fix anything, I was merely trying to help you troubleshoot exactly where the error was being generated. But that's...

In my mind, there is a logical separation between the function of the JOIN clause (joining tables together) and the WHERE clause (filtering the data that is returned). Shovelling everything...