>>To dispell any illusion that I may be any kind of expert on Access: I spend about 20 minutes a year in it, mostly looking at the data to convert. Beyond that, I touch it only with lead gloves, aka ODBC connection :). So... whatever is its equivalent of dbsetprop() or what it may have - you can search for its DML just as well as I can, and, ahem, this baby is your problem, not mine :). OTOH, see the first paragraph - if text is to be entered anywhere and they know what it should be, let them do it.
>
>20 minutes a year? More then one ks? This adds up to endless hours! ;)

I never dared totaling them. My beard is white already, but hair still isn't and I'd like to keep it that way for as long as it naturally holds. So, no shocks if possible.

>If they do it I can not charge them?

Typing captions is, ahem, not the highly qualified job that you can charge much for. But I see your point...

>The captions are changable in my app too ...
>
>And somehow I hate the modern help system. VFP is fine, I can deal with man pages, but the web based stuff MS is presenting I'm not warm with.

It's not the medium, it's the message. Office help was just as ridiculous when it was in the .hlp and .chm format. Imagine that help for excel 2003 didn't know what rgb function is... it did mention it in examples elsewhere, just didn't know that it has specific help for it. Nowadays it's not just help, it's just about any msdn/kb article out there that's almost content free, where 90% of the text consists of legalese ("applies to products" etc) and the rest is carefully wrapped in an alegoric language where they never call spade a spade, so yes, it's an exercise in frustration. There's a whole biocoenosis off MVPs and other gurus helping people wade through that jungle. Again, it's not the medium, it's the content.

>I guess I will travel to the customer and see if MS ACCESS has an macro recorder like EXCEL - my best way to learn EXCEL Automation [eg].

The only way... let us know how it ended.