You may want to check permissions like CornerAnalyst suggested. However, I think you would get a different error message if it were permissions.
Here's another
MS TechNet forum thread. It's for VB.NET but I think the points in that thread can apply to VB6 too. The two points that might cause that error are inserting a null value to a "not null"-field and explicitly disposing data-adapter commands. So in the case of VB6 the issue may come from any previous command (or command object to be more precise).
Also, the SQLProfiler was mentioned. It might be worth to try to see what actually happens.
Reputation Points: 218
Solved Threads: 201
Veteran Poster
Offline 1,024 posts
since Aug 2008