Yeah, neither of them are 0, and I dont think it does any division.....

What bothers me, is VB is probably "masking" the error. It's probably to do with something I gave an OGL call, and then it's in line #4 or something of that code, so it goes 4 codes down in MY prog, so it says that that is the error....

The strangest thing is, (like I said at the top), is that it works the first time around, but not the second...