Release vs. Debug mode builds

Hi,

I ran into a very peculiar problem with my project. If I build it in debug mode and run the .exe from the debug folder I get the following output with this line:
[code]
fprintf(out, "%d %s %s %s%c", DD.vectWords[i].Bits[j].Bit,
DD.vectWords[i].Bits[j].WarMsg,
DD.vectWords[i].Bits[j].Destination,
DD.vectWords[i].Bits[j].Type, c);

Code:

---

---

output:
11 "take off" CAS WARNING

Which is what it's supposed to be. If I build in Release and run the .exe fro mthe Release file the same line of code produces this:

Code:

---

125634
34
.
3545

---

Or some other gibrish. I couldn't find any info about the modes and I don't know this well enough.
Does anyone else know and could tell me how to fix this and what/why's happening, please?

Thanks

Edit: I forgot to mention that I run Windows NT and MS Visual C++ 6.0

??????

Well, if the problem can't be fixed is it oKif my application is built in Debud configuration? The users will just use the .exe fiel and just run the application.

I believe Microsoft doesn't allow you to give Debug builds to customers. Besides, the fact that it doesn't work in the Release build means there is a bug, and that bug might seriously corrupt the user's data under different circumstances even in the Debug build.

Make sure that i and j are initialized and are within the bounds of the array/vector. Debug builds often initialize uninitialized variables to 0, which might be why it works.

That goes through a double for loop of the following form:

Code:

---

for (j=0; j<19; j++)

---

and they are used earlier in the function.

And the Bits array/vector has 19 elements? If its a vector, write out its size to verify, and do the same with vectWords. I'm just grasping at straws, there are many different possible reasons.