Daniel,
Something to keep in mind is that when you BROWSE a cursor/view and that cursor/view is in row buffering mode, any buffered changes will attempt a save to the back end. If that save fails for any reason (PK violation, update conflict, etc.) the BROWSE will also "fail." Check out help on using AERROR() to figure out what's wrong.

We've found that your best bet is to avoid BROWSE altogether in this case, open the debugger and use GETFLDSTATE(-1, YourAliasName) to find which fields have changes.

Hope that helps,
---J

>Sometimes when working on a view, I preform some certain operations. The operations vary and I don't think they are of any consequence. The odd thing is when I issue Browse to look at the data, no browse window appears. Why is this?
>Thanks,
>Daniel