>Hi Stephen:
>Yea, we have been using MM .NET Framework for about a month. We went to Little Rock for a software conference and I went to two of Kevin McNeish's MM sessions. In general, they have done a clean job and they have a good manual.
>
>I thought the error was due something in MM but now it looks like it is generated by
>SQL Server 2000. Michel Fournier suggested Googling the error; this shows that several other have had the same error. Maybe it is time to upgrade to SS 2005. Anyway, it appears to be row related. With a recordset you could step through each data item and find the error but with a dataset, I don't see how to do this.
>
>Is there any one else in town using MM? We could start a local MM/VS user's group.


Clark Brown, but he would not come out to a UG meeting.

I'd like to see if Kevin would come to Memphis for a Dotnet meeting. I've know Kevin for about 7 years now.

I'm working on an Access conversion right now. It's killing me to attempt to hit a May 1 deadline. No normalization in the access data, and poor design of records. Does the term flat file sound familiar? 1 table with a few 1:M tables as well as a few look ups :)