On Wed, Jul 24, 2013 at 9:17 AM, Tracy Pearson <[email protected]>wrote:
> Tracy Pearson wrote on 2013-07-24: > > Jeff, > > > > This has happened from time to time with a few of our clients. The XL5 > was > > created from Office 2010 and saved as an older version. The older > version > of > > Excel will open it, the import process fails. > > > > Sometimes, when VFP is closed by the OS, an error file created where the > > runtime file exists. Most of the time that I've seen one of those, it > points > > to the READ EVENTS line. Which suggests an error occurred in an event > > routine with an ActiveX control on a form. Sometimes it has pointed me > to > an > > exact line of code. > > > > I meant to include, our import allows CSV as well and this was the work > around for them. > ------------------- > Why not use ADO and query the excel file as a data object from now on? This was as Office365 or any other new version comes out. You are safe. -- Stephen Russell Sr. Analyst Ring Container Technology Oakland TN 901.246-0159 cell --- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html --- _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/cajidmylgaqskbk16c87djmckatgt11ics53c-64_prhjwvx...@mail.gmail.com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
