Looks suspiciously like one of those two variables overran the length of the array, but really, it could be many things (like a freed pointer not made null). It would have been best had you left your database in the crashing state so that you could reproduce the bug and hopefully figure out what was going on. VC has typically been very good (at least VC6, the last version I've used) about debugging. If you can get it to crash there again, examine the state of the variables and objects. Try to figure out what's going on. And there may not be anything wrong with that line, just the state of the system when it gets there.
However, if repopulating the DB did make the problem go away, that probably means that the code works in good scenereos, but crashes in exceptional cases (instead of failing gracefully).
|