Click here to Skip to main content
15,847,549 members

Comments by Daniel Miller (Top 7 by date)

Daniel Miller 12-Dec-15 15:15pm View    
Reason for my vote of 5 \n This is a very thorough list of useful tools - thanks!
Daniel Miller 21-Oct-15 10:05am View    
To confirm then, you are no longer getting an error, and the tables in SQL Server are successfully created and loaded from Access, but the primary key column in the new tables does not have the Identity property enabled - is that correct?

If so, then this is a resource you might want to check:
http://blog.sqlauthority.com/2009/05/03/sql-server-add-or-remove-identity-property-on-column/
Daniel Miller 20-Oct-15 10:33am View    
You don't need to create the destination tables, and you don't need to worry about setting IDENTITY_INSERT in your stored procedure.

"SELECT * INTO" will create the table and correctly load your data from the source tables.

I don't know what error you are getting, but I think you should remove "SET IDENTITY_INSERT '+@table1+' ON;" from the code in your stored procedure because that is the most likely source for an error.
Daniel Miller 19-Oct-15 13:21pm View    
Thanks, I appreciate it. I have been 'lurking' on the CodeProject site for years because it's such a great resource, and recently I decided I ought to begin contributing something back to it, so I am working to develop and improve a reputation in the community here.
Daniel Miller 19-Oct-15 12:42pm View    
Fair enough - point taken.