So you got it right then?

Sorry - I meant for you to replace 'fieldlist' with your list of fields to be selected.  Fieldlist is not a keyword

select distinct

will return unique rows, at field-by-field level.  If any of the fields in the rows are different, the row will be returned.  Therefore the fewer fields you return,...

Aha - never had to work with huge text fields - over to someone else!

Yup, I was talking twaddle once again.

Best go home and swat up

Phil

Prob not the dept table, as that is not included in the section of your code which is causing you problems.  Update: there is no dept table - you...

Please post some sample data (just the relevant fields will do) and datatype/size of text fields.  No need for full text indexing.

Regards

Remi is right.  What is your objective?  It is easy to write a SELECT query to display the data how you want.  Or you can create a permanent VIEW of...

Maybe you could try reproducing the problem by running in Query Analyser - this way, you will narrow down where the problem is going wrong - obviously the SQL itself...

Try the Table Analyser Wizard in Access - haven't used it, but looks like it targets your sort of situation.

Regards

As SQL Server 2005 (not 5000) is not yet out of beta testing, there will be very few businesses using it for production purposes, whereas there are thousands using SQL...

Creating the table structure isn't hard - it's easy to get yourself a CREATE script, if you already have the table locally.  Just browse to the table in the Query...

What are you trying to do exactly?  It is possible to trim the time bit from a date before storing it in SQL Server, if that is your requirement.

Regards

Define 'weird result'!

I assume CompanyID is unique in Company?

Is DepartmentID unique to the Company table?

Regards

Can you send the data in the format 'yyyy-mm-dd'?  This format should work regardless of American/English date worries.

Regards