Gaulin, Mark wrote: > Ok, so how is the varchar field defined? If it is over that limit you > mentioned earlier (1000 or so?) then that's the problem. Basically, SQL > Server would be complaining only when the data to index actually was too > big. > > I suspect that's the issue - in this particular table, the varchar field is set at 2000.
I'm currently in the middle of reworking things so instead of having one raw 'data' field, I have several of different datatypes (datetime, varchar, text) and store the user data in the appropriate column based on data size and type. I'm hoping that'll take care of this issue. The trick is - the data field in question isn't indexed. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Upgrade to Adobe ColdFusion MX7 Experience Flex 2 & MX7 integration & create powerful cross-platform RIAs http:http://ad.doubleclick.net/clk;56760587;14748456;a?http://www.adobe.com/products/coldfusion/flex2/?sdid=LVNU Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:268110 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
