>I understand that I can open manually with Excel. However, this is an automatic program running on a web server that formats the data and sets it in a queue for the client to process. The translation is all automatic based upon the conversion routine assigned to the sender. Forcing my client to open the file and save to Excel, CSV, etc. would circumvent the process and cause a lot of extra work on their part. Ideally, there will be a way to convert the data programmatically.

Did I said, manually?
:-)))))))))))))))
If there is an Excel installedm you could open that file with Excel, save it as XLS and then import it in VFP.
All with Automation.
I'm afraid there is no other way.



>
>
>>>I have a website that collects files from clients and translates them into a format for our UNIX server. I was just handed an ods file for the first time today. I can open with Excel 2010, but VFP doesn't seem to have any knowledge of this file type, which makes sense due to it's age.
>>>
>>>Is there a third party add-on that will allow me to translate ods to a vfp cursor for processing? I don't think Office is installed and I've never tried automation of open office. Or is it time for a custom .NET dll call from VFP? I would love advice from anyone who's tried this so I don't go down a bunch of dead-ends.
>>>
>>>Thanks!
>>
>>This is not because of age of VFP.
>>This is just because OO is NOT a MS product.
>>I doubt in .NET there is a native way to import a OO file.
>>What is installed on user computers?
>>If Excel you could open that file with Excel, save it as Excel XLS and then import it with VFP.