AlphaDAO Excel export

[Bill Parker]

I saw Stan's recent post on the 16384 limit, and using that approach does allow me to save an .xlsx file and open is successfully. But naturally I am using AlphaDAO for some other gymnastics I am doing. I have used this code for some time, but was exporting to .xls. Trying to change to newer format, but get the attached error when trying to open the file with Excel 2013.

Here is the first part of the code generated by the genie, saying to use Excel 2010.

dim connectionString as c 
connectionString = "{A5API='Excel',A5Syntax='Excel',FileName='D:\A5v4\AMSC\v5 Combined\from AMS W2 20160929\test2.xlsx', A5ExcelVersion=2010}" 

delete options 
dim options as p 
options.ConsolidateArguments= .t.
options.ShowProgress= .t.
options.AllowCancel= .t.
options.TableNamePrefix = ""

delete a_export
dim a_export[0] as p 

a_export[].LocalTableName = "charges.dbf"
a_export[..].TargetTableName = "charges"
a_export[..].TargetTableOwner = ""
a_export[..].ExportFields = <<%txt%
Person_Id

Is there something simple I am missing to get the export in xlsx format?

Bill.

[Stan Mathews]

Re: AlphaDAO Excel export

That is odd, Bill.

I ran through the creation of an export and encountered the same problem.

During several diagnostic attempts I used the Create Database button during the Define connection string process, Build. On one of those attempts I neglected to enter the .xlsx extension. The resulting xbasic

{A5API=Excel,FileName='P:\test\nw_atest',A5ExcelVersion=2007,A5ExcelVersion='2007'}

still works but the output is a file with the .xlsb extension, which will open.

I'm not familiar with what that extension might indicate.

Image 8.png

Note: changing the xbasic to

{A5API=Excel,FileName='P:\test\nw_atest.xlsb',A5ExcelVersion=2007,A5ExcelVersion='2007'} also creates a usable output file.

as does

{A5API=Excel,FileName='P:\test\nw_atest.xlsb',A5ExcelVersion=2010,A5ExcelVersion='2010'}

[Bill Parker]

Re: AlphaDAO Excel export

So google says it is a binary file type, like xls. It is supposed to be faster and smaller than xlsx, but you can't tell up front if it contains macros. I can see tha it could be useful to have this format as an option, but for files that will be exchanged with others, xlsx is likely the better choice.

I'll see if Selwyn thinks this is a bug.

Bill.