this code with the minor changes required passes syntax for SQL2005: i think the issue was there was select min(select somevalue) instead of select min(somevalue)

set ANSI_NULLS ON

set QUOTED_IDENTIFIER ON

go

CREATE TRIGGER...

by default SQL server treats anything between single quotes as a varchar; it' doesn't try to determine whether the varchar may also be a date...that's the behavior you are seeing.

so...

ADODB is part of the microsoft Data Access Components (MDAC)

here's more info and the download:

Download details: MDAC 2.8Microsoft Data Access Components (MDAC) 2.8 contains core Data Access components such as...

syntax wise, there was an extra single quote near SessionComplete, and the @startDate/E@Enddate were not declared inte snippet you posted. no problem there.

the statement you pasted only references one table,...

it's gotta be a translational error instead of a copy/paste error; it's not adobe, like adobe reader.

it should be

Set Conn = CreateObject("ADODB.Connection")

ADODB is the standard way I've always connected to...

results into excel, and getting excel to run a stored procedure or query text is pretty easy.

i made this in an excel worksheet for Excel 2002.

to recreate, simply open excel,...

i was just about to post the same thing as michael did...if the table has definitions for decimal 20,10) for example, it keeps 10 characters...you really want 7 siginificicant digitis,...

i thought float,real and numeric were non-deterministic so you get approximations like 3.99999999999999999994 for the value of 4.00 stored and such...., and it was better to use money or decimal...

Ramesh that was spot on... the only thing that was missing from your sample was a single character due to my poorly named variables:

WHEREN <= LEN( T2.DefinitionAsHTML )AND SUBSTRING( T2.DefinitionAsHTML,...

Thanks Ramesh; i'm looking it over now; i must have got a copy paste error, as it returns an erro based on something in the data;

Conversion failed when converting the...

stating the obvious, you can't have SQL server watch itself..if it goes down, it can't report. you need something running with the operating system.

I know over at sourceforge.net there is...

a SQL 2005 database, no matter what compatibility level it was set for, is still in SQL2005 format, and can't be restored or attached by previous versions of SQL.

compatibility level...

two things i could think of checking are:

check the table for a trigger...maybe a trigger is changing the bit field...

check and make sure the field isn't a calculated field, and...

this will KILL you if you are searching a database that has a table with millions of rows..

this works really well whens earching for data like you describe:

CREATE PROCEDURE UGLYSEARCH...

several ways, but information_schema is the recommended practice:

select TABLE_NAME,COLUMN_NAME,* from

INFORMATION_SCHEMA.COLUMNS

WHERE COLUMN_NAME like '%native%'

select OBJECT_NAME(id) as Table_Name,name as ColumnName from syscolumns where name like '%native%'