>>The example PRG is for demo only and I use it to open the table. The methods SaveTableToWorkbook() and SaveTableToWorkbookEx() both take the first parameter as the alias (or table path). If you pass the cursor alias name to the method as the first parameter then it will use that as the source for output. If you pass a table file name with path that is not opened then the method will open and close the table for output. The SaveTableToWorkbook() method outputs all columns of the alias passed; whereas, SaveTableToWorkbookEx() allows you to pass an array containing the names of the fields (and column names) to be outputted.
>
>Thank you very much! Yes, I replaced the first parameter with the cursor name and it works!
>
>A cursor with about 2200 records and 52 columns/fields take about 1 minute to export. I am not at all complaining about the speed; the customer will wait whatever is necessary. But, in your opinion, is this normal amount of time?
>
>Update: Please confirm my understanding that in order to use your library I need to include in the project the "vfpxworkbookxlsx.vcx" and nothing else, right?
>
>Update2. I noticed that the book name in the resulting .xlsx file is actually the name of the cursor. And in my case the name of the cursor is sys(2015) so it looks like "_48445354". Is there a way to specify a book name in English so that it looks readable (by the customer)?

Come ON!
Above you moan about a 80 page doc and here you write before probably even looking at the source code ?

As such a naming option makes sense, there is a good chance of it already being implemented and documented - if you are too lazy to

- check out the docs

or

- follow a breakpoint from your call,
- try out an enhacement with an optional parameter
- and offer that source change back to Greg, pehaps even with updated docs,

why not use the cursor table AGAIN with a fitting name ?