I have an SQL 6.5 (Enterprise) database, which is referenced by a VB6
application using ADO. Both the application and DB were written by an other
A few days ago, the VB6 application crashed and it appears to have left the
DB in a bad way. Whenever the application tries to insert an entry into the
Journal table the DB raises an error saying that the constraint on the
primary key is being broken by a duplicate value for the primary key. The
insertion is performed by calling a stored procedure. There have been no
source code or DB changes inthe recent past. The system had been running for
several weeks without any problems.
Could somebody please advise me on the best approaches to take to solve this
problem. I have access to the application source code, Visual Basic 6
Enterprise Edition, and the SQL 6.5 server.
All responses appreciated,
Keith Lomax MCSE MCP+I