>>Pardon me if I'm stating the obvious elephant, but... could it be that the fourth record was still only in the buffer and not yet with a parameteri into the table? Then a view against that table would show only the records which made it to the disk so far, i.e. only three. Just closing the entry form would flush that and then the view would show all four. So, perhaps a tableupdate() still didn't have a chance to do its trick at the time?
>
>Don't you think it should be flushed into the table as soon as I get out of that form? So why only 3 records when I open another form that will get the records from a parameterized view to print the report?

I'd say it's worth a try - obviously the fourth record is still not on disk so far, so try with flushing it.

Mind you, it's been a while since I had something of the kind, because I've put calls to .save() before any action that takes me out of context - be it navigation to a different document, activating a different form etc etc, anything that may cause the user (me) to forget to click save (and I still have one place where I forgot to do that... and keep forgetting to fix it).