>> By WTF I mean the multple if's and cases and record by records checks on mulitple fields (walking the file)

Record-oriented processing is not one of SQL Server's strengths and I've only come across a few processes that require it (Tree traversals comes mind). A set-oriented operation would be preferred when working with SQL Server.

With that said, you might want to refer to An Overview of SQL Server "Yukon" for the Database Developer (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsql90/html/sql_ovyukonnetprogfeatures.asp), specifically to section ADO.NET: Server Cursor Support (SQLResultset).

-Mike

>Neil,
>
>But in t-SQL --- Walking-The-File (WTF), which (with my current knowledge, just beyond rank newbee) is very next to impossible, the clr will should at least allow this. Testing will need to be done but this for my Anomaly system is absolutely required ...
>
>By WTF I mean the multple if's and cases and record by records checks on mulitple fields (walking the file) just what VFP does best is sorely needed. The only isssue that sort of spooks me is new processing required at the server. but if the data stays at the server and the network trafic doesn't get involved could actually be a plus compared to VFP (maybe??)
>
>In all honesty I very intrigued by this clr in SQLServer thingee and for the first time in 10 years have looked at sql-server v VFP for data processing not just storage!
>
>
>
>jp
>
>
>>Simon,
>>
>>The CLR is hosted by SQL Server and is loaded the first time you invoke a .NET function. You create your .NET assembly and expose its functionality by registering the assembly with SQL Server and defining a function or procedure that can then in turn be invoked.
>>
>>There will be overhead in not just loading but all that comes with the CLR like JIT, again this is where you must clearly understand when an where to use managed code.
>>
>>http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsql90/html/sql_ovyukonnetprogfeatures.asp
>>
>>HTH
>>Neil