>>The field names defined are none-speaking, those are just my internals. Before they hade speaking like [Field "A" in %] what looks like some upsizing from EXCEL to ACCESS using my captions ...
>>
>>There are speaking captions available
>
>Yes, in Access they can rightclick each table, select "design", then enter captions in the property sheet for each field - caption is a property. A kind of GUI as good as any other.
>
>>This is a larger number of fields, so the customer, who can handle the database with Access, is not happy to put the captions on the fields. There is some sort of caption or description for MS Access fields, I have no idea what.
>>Customer is not of much help, they are non IT folks. But they say there is some sort of information the enter so it apears on top of the colums, no matter how the column is named. Just like VFP table columns Caption property, if used in a DBC.
>
>Yup, it should behave the same, AFAIK.
>
>>(Again I know nothing of MS ACCESS. I can handle some basic SQLs but that's it.)
>
>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! ;)
If they do it I can not charge them?
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.
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].