just a though. you're using labels to show this data - not text boxes?

but i'm guessing since you're getting #name thats not the problem.

looking at it though - you're using...

use a union query

select cutomer_id,max(orderdate) from mytable group by customer_id

UNION

select customer_id,max(orderdate) from mytable where custorders.id not in

(select id from custorders where ..........

i always use convert(varchar(11),getdate()) to put the value out in a real date format.

then convert it back to datetime

hence

select convert(datetime(convert(nvarchar(11),getdate()))

returns '12-may-2006 00:00:00'

not sure if this is right - but you might have to use

dim param1 as NEW adodb.parameter

although after a beer at lunch i'm not sure

is the login a member of builtin/administrators?

if the service is failed over on node 1 where your user login is a member of local admins, but not a member of...

depends on the table structure

but normally for the 1st 100

select top 100 * from mytable order by dateadded

then for the second 100

select top 100 * from mytable where...

I have to say that i think i agree with your developers.

this seems to be very open to interpretation, but i think that if you have table values that are...

which hotfixes?

i think 2162 was withdrawn for a few months and then replaced because it was faulty.

exactly right.

always always enforce referential integrity through the db. if your app fails because of DRI then its not a good app

mostly developers don't use foreign keys and constraints because...

yes you can

but it will usually end in someone crying

the sql server will also protect it from executing endlessley and will stop it at the nesting level set...

i just tested it as i've not seen these scripts before and have no problems at all - no x required.

are you using the revised version posted most recently?

other than...

select * from table1 where field1 like N'% %'

you could also do something like

select * from mytable where field1ltrim(rtrim(field1)

but this would be very bad against large tables

also

select * from...

create proc myproc @unit nvarchar(10)=NULL,@invdate datetime=NULL,@invno nvarchar(10)=NULL

as

declare @strsql nvarchar(1000)

set @strsql='select * from mytable where 1=1 '

if @unit is not null

begin

set @strsql=@strsql+' and unit='''+@unit+''''

end

if @invno is not null

begin

...

i do agree with the other guys here - set based is always best but sometimes you don't have a choice

the only way i can see you doing this is...

you might be able to find a lot of this information (and more) by downloading sqldiagnostic manager from idera.com

there's a 28 day free trial and it's about £600 ($1000) per...