This is starting to become more of an issue.. that I need to figure out as soon
as possible. And I really have found no good fix  to it. It's simply that in a
calculated field, sometimes the Version number  blanks out?!? Any ideas..
Anybody?

I suspect you are running into a timing issue  where the field  is being
calculated and the version  number updated simultaneously when you save an
item. The easiest way to fix  this would be to update the Calcuated field
using an ItemUpdated event receiver. That way the version number  will be
set before the calculated  field is set. I don't know any way to enforce
that timing using the built-in Caculated field.

I get what you are saying. And most likely you are correct with your
suspicion.

I think I may just work around this in a different way though, I do have a
workflow that runs to publish a major version, so I will just do my own
calculation/update of that field  at the point.

since workflows always kick off after the
item is saved.