>To further confuse the confusion, here are the updatestr values from two of my pages, the first from the page that is not working; the 2nd from a page that is. I can find no differences in the updatestr (indeed, they both work when pasted into iSQL) or in any other part of the text. But there must be a "difference" somewhere ..... right?
>
>// the insert updatestr from "broken" page
>insert into corecomponent
> (component_name,component_description,component_class,create_date,
> create_userid,uniqueness_column,manager_type,component_status)
> values ('ADD TO LANE ','DESCRIPTION FOR LANE',3 ,'11/16/00 9:51:33 AM','combsv',
> '_11/16/0095133',0,59)
>
>//the insert updatestr from working page
>insert into corecomponent
> (component_name,component_description,component_class,create_date,
> create_userid,uniqueness_column,manager_type,component_status)
> values ('NEW COMPONENT','DESCRIPTION FOR COMPONENT',5,
> '11/16/00 9:52:54 AM','combsv','_11/16/0095254',0,59)

Definetly, the problem is not in the query (you said you runned it in iSQL).

The next step is to check properties of the connection and the command object for both queries (the good and the wrong). Are you using using the same connections for both queries?