Oh I hate this sort of thing. I have an access database that has been working fine, but then, with no input on my part, decided spontaneously to change its behaviour so that calculated fields no longer display. I found the explanation:
It turns out it's a known (and now at least acknowledged) bug, for which it doesn't look like anyone at Microsoft has been able to come up with a solution. I'm really irritated because I've put a lot of effort into this Access application and now we're having to explore options as drastic as giving up on Access altogether. It's a huge mess.
It turns out it's a known (and now at least acknowledged) bug, for which it doesn't look like anyone at Microsoft has been able to come up with a solution. I'm really irritated because I've put a lot of effort into this Access application and now we're having to explore options as drastic as giving up on Access altogether. It's a huge mess.