>>The only safe way to have our custom-made browses appear the way we want them is to write long-sausage Browse commands, field by field (or invent some sort of builder which will create parts of them on-the-fly) - but then, we may be better off going for the grids in the first place. They have better builders, right?
>
>Yeah, I don't do BROWSE in apps. Too many headaches and data integrity holes. Plus, I don't like to explain to users how to look at raw data.
>
>She said this was a FP 2.6 app so there is not many options. Your mention of the long, hairy browses with all the formatting options/switches brought back bad memories. < g >

I actually had to write a browse command builder, which was nearly as ugly and complicated as the thing it built - but was still easier than doing it manually. My point still holds: if you want the browse under your control, you have to have the long monster in code. Everything else is just waiting to vanish, being based on foxuser.dbf.