Correct, and only adding records with an IDENTITY specification on a column in the table... however, that's generally about 90% of your tables, and if you can't add records, what's the point, how are you going to delete or update them?

So with the framework as is there is no way to get around this in SQL Server 7.0. Editing or deleting existing records is no problem, just adding. Correct?

Well, Mike, this one gets a little ugly... the problem is that your database is on SQL Server 7.0, and 7.0 doesn't support SCOPE_IDENTITY() or IDENT_CURRENT(), but only @@IDENTITY. We have to use one of those three methods to retrieve the newly assigned identity value for the primary key on your table, but we cannot use the @@IDENTITY because of trigger problems (see http://codebetter.com/blogs/john.papa/archive/2006/04/07/142503.aspx). We don't have a SQL Server 7.0 machine setup for us to unit test on, and we may need to add a compatibility mode for SQL Server 7.0.



However, even if we add the compatibility mode, there's no telling what else might break. You best bet is to move to at least SQL Server 2000, even if only for the performance and feature enhancements, unless you're absolutely stuck on SQL Server 7.0.

I was trying to add a new record and this is the error I got. Not sure where to go from here. Let me know what else you need to know.



Thanks