It's not necessarily Display Status functionality that we criticize. I would imagine that, at one point, I'd like to know what tables are open and what's their status when the error occured. Of course, using .FormCount and SETting DATASESSION TO every form's DataSessionId would get us closer, but the duckling is still ugly.
To conclude, I (as a novice) think it would be very helpful, as you (George) mentioned, to have forms, at least those using Private Datasession, log themselves into a tablelike structure where they can be referenced when needed.

Sorin

>Now that's a nice can of worms, isn't it?
>
>One solution I can think of would involve retrieving all the open forms, and using AMEMBERS() to examine the .DataEnvironment. I guess the .Forms and .FormCount properties could be used, but I haven't figured out the actual mechanics. Otherwise, you could have the forms register themselves in a cursor or file.
>
>Display Status? No offense intended, but that seems, well, ugly. Of course, if it works, the duckling turns to a swan pretty quick.
>
>George