>>>I'm not an expert for SCX/DATENVIRONMENT, I use forms via VCX and add my DE's at runtime, and do all datahandling by CursorAdapter, skipping all this inner workings. It was to ugly to maintain.
>>>
>>>So you have
>>>- a form with a DE
>>>- the DE holds one cursor object for your table
>>>
>>>This table is open and holds all the records you expect, right?
>>>
>>>And then you run a VIEW against that table, or is this a different object in your dataenvironment?
>>>And this does not show the number of records you expect?
>>
>>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?

If you have the cursor buffered (use CURSORGETPROP() the read the state) and do not code a TABLEUPDATE(), it will not update. If there is no buffering, then it's written directly to the drive. There are odd moments where a FLUSH might work, but this very rare.
Else I pointed out all stuff I would test. I still think the most likely is an error in your WHERE / ON expressions.