Windows 7, Accuterm 2k2, and XLSX extensions

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

   Hi All,
We're having a problem transferring via FTD to an XLSX file type. We've upgraded Accuterm on our system to 2k2 Release 5.3c (AIX and PC side). When we transmit the file, it accepts XLSX as a valid file type, yet we are unable to open the resultant file with Excel 2007.
If I manually change the file type to XLS, it will then open in Excel (but we're stuck with the 65k lines limitation).
Anybody have any ideas on what may be going on here?
Roland

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
rosic Members Profile Find Members Posts Newbie Joined: June 12 2007 Location: United States Status: Offline Points: 7	Post Options Post Reply Quote rosic Report Post Thanks(0) Quote Reply Topic: Windows 7, Accuterm 2k2, and XLSX extensions Posted: May 25 2010 at 3:44am
	Hi All, We're having a problem transferring via FTD to an XLSX file type. We've upgraded Accuterm on our system to 2k2 Release 5.3c (AIX and PC side). When we transmit the file, it accepts XLSX as a valid file type, yet we are unable to open the resultant file with Excel 2007. If I manually change the file type to XLS, it will then open in Excel (but we're stuck with the 65k lines limitation). Anybody have any ideas on what may be going on here? Roland

PSchellenbach Members Profile Find Members Posts Admin Group Moderator Joined: December 15 2003 Location: United States Status: Offline Points: 2150	Post Options Post Reply Quote PSchellenbach Report Post Thanks(0) Quote Reply Posted: May 26 2010 at 10:53am
	Hi Rosic - Are you running 5.3c or 5.3c-sp2? The .xlsx support was added in sp2. Thanks, Pete

lausdsbio Members Profile Find Members Posts Newbie Joined: November 23 2015 Status: Offline Points: 1	Post Options Post Reply Quote lausdsbio Report Post Thanks(0) Quote Reply Posted: January 21 2016 at 6:57pm
	I am running 5.3c-sp2, and I have not been successful in downloading a usable .xlsx file - meaning when I try to open the file I receive an error message: "Excel cannot open the file 'temp.xlsx' because the file format or the file extension is not valid. Verify that the file has not been corrupted and that the file extension matches the format of the file." Thanks for your help.

pellitieri Members Profile Find Members Posts Newbie Joined: January 27 2016 Location: Toledo, Ohio Status: Offline Points: 6	Post Options Post Reply Quote pellitieri Report Post Thanks(0) Quote Reply Posted: January 27 2016 at 1:09pm
	I upgraded from 5.3b (5.3.210) to 7.1b sp2 (7.1.2012). Both version are installed under Windows 10 in separate folders (C:\Program Files (x86)\Atwin and C:\Program Files (x86)\Atwin71). At this time, I am the only user on Version 7.1b sp2. I have not updated the FTBP files on our system. I get the same error message as lausdsbio when I try to open the xlsx file. If I rename the file to have the xls extension, it opens properly. Is it possible that we're launching the wrong conversion program? If so, is there somewhere I need to redirect this? Any help would be appreciated. --Tom Pellitieri - Century Equipment - Toledo, Ohio

PSchellenbach Members Profile Find Members Posts Admin Group Moderator Joined: December 15 2003 Location: United States Status: Offline Points: 2150	Post Options Post Reply Quote PSchellenbach Report Post Thanks(0) Quote Reply Posted: January 27 2016 at 5:46pm
	Hi Tom - What version of Excel do you have installed on the machine running AccuTerm 7? Is it possible that Excel options are set to save in "compatibility mode"? Thanks, Pete

pellitieri Members Profile Find Members Posts Newbie Joined: January 27 2016 Location: Toledo, Ohio Status: Offline Points: 6	Post Options Post Reply Quote pellitieri Report Post Thanks(0) Quote Reply Posted: January 28 2016 at 6:37am
	Thanks, Peter!! I have Office 2013, but many people still have earlier versions of Office, so I had my Excel Options \| Save \| File Format set to xls by default. I changed it to xlsx and the export worked. Again, thank you! --Tom