Excel 97-2003 To Xlsx

4 views

Skip to first unread message

Cesar Sergeantson

unread,

Aug 3, 2024, 4:42:03 PM8/3/24

to terlipimas

Hello Alteryx Community. I was wondering if someone could help out with this inquiry. My workflow is generating Microsoft Excel 97-2003 Worksheet as the output even when the workflow has been set up to produce xlsx files. I also checked on the input files and none are Microsoft Excel 97-2003 Worksheet.

What data do you have in the Vendor Names field? When I use the "Change Entire File Path" option, I'll have a field with "G:\\.xlsxSheet1" or something like that. If yours is set up that way, is it possible that it has .xls instead of .xlsx?

I'm trying to import my excel file as a data table but apparently the version of excel used is too old. It says: "There was an error opening the file in the Excel Wizard. Files older than Excel 97 might fail to open. Using the Open All Sheets preference should work in this case."

if an Excel file is older than Excel 97, JMP will try to use some much older code to open an Excel 5.0 file. That is only available through Open All Sheets. However, files earlier than 5.0 often fail to open at all. The simplest solution is to open the file in Excel and use File->Save As to specify either Excel Workbook (XLSX) or Excel 97-2003 (*.xls). Then save out the file using a new name or overwrite the existing file. JMP can now open the file.

One general suggestion ... rather than trying to import the whole Excel sheet (which includes a lot of title stuff, etc), I recommend to always specify just the range of cells with the data. And then once you're doing that, I also suggest using getnames-yes. The spreadsheet will generally import much more cleanly & usable, when you specify the range. For example:

In this specific case, if using dbms=EXCEL isn't working on one particular computer, I would recommend bringing up the spreadsheet in Excel, and then re-saving it in the older "Excel 97-2003" format (the extension will then be .xls rather than .xlsx). And then you can try using SAS' dbms=XLS, which I believe uses code which SAS developers wrote to import the spreadsheet (whereas I believe dbms=EXCEL uses the Microsoft Jet engine ... or something like that).

We used to be able to export issues to Excel file format from the Jira Issue Navigator (search and filters). After our company upgraded our PCs to Windows 10 and Office 365 few months ago, we are no longer able to open the Excel files exported from Jira. We're running Jira Server 7.10.2.

"Excel cannot open the file 'XXXXXXX.xlsx' because the file format or file extension is not valid. Verify that the file has not been corrupted and that the file extension matches the format of the file."

It's an older story. The problem is that the "xlsx" file exported from Jira is actually an HTML file with a table, which older Excel versions were able to import. So it was never a native Excel file, but the file extension instruction Excel to import it. Then, Microsoft disallowed this trick for security reasons.

Open excel and go to the options/trust center/trust center settings/file block settings and look for any file for some earlier versions of excel being blocked. I had a similar problem where older versions of excel were blocked for security reasons.

BI Publisher currently allows Excel templates only in Excel version 97-2003 (*.xls). Please update the BI Publisher software to accommodate the current version of Excel (*.xlsx). This will avoid issues with 65K records per sheet as well as provide other benefits of current Excel files. Thanks.

Reporting on cost transfers - currently required in BI Publisher due to limited availability of data in the OTBI subject areas. A departments cost transfers must be reported and the current report generates 68 sheets within a single workbook making the user experience minimal at best.

This feature is a must for my client UKRI as well. BI Publisher currently allows Excel templates only in Excel version 97-2003 (*.xls) in Oracle Fusion, and this version can only accommodate first 3 conditional formats and we need more than 3 conditional formats in our Time and Labor reports.

LinkedIn and 3rd parties use essential and non-essential cookies to provide, secure, analyze and improve our Services, and to show you relevant ads (including professional and job ads) on and off LinkedIn. Learn more in our Cookie Policy.

When creating Excel workbooks there are a large number of file type options to choose from. Some are best reserved for the importing and exporting of data e.g. TXT, CSV, PDF, and some for specific/legacy functionality e.g. templates, add-ins, and even the legacy XLW Excel 4.0 filetype which can be opened in Excel 2013 and later but not saved.

XLS - the binary file type for Excel 5.0/95 and 97-2003. You're still likely to encounter these on a regular basis. Where possible they should be converted to a newer file type to both save disk space and take advantage of newer Excel functionality. The only benefit of this file type is its backward compatibility with older versions of Excel (2003 and prior). Its disadvantages are a larger file size and smaller row/column limits than newer formats (65,536 rows and 256 columns), and no ability to use newer functionality. It's also not possible to tell from the XLS file extension whether the workbook contains VBA macro code.

XLSX - the XML file type. The default file type for Excel 2007 and later, documents are saved in an XML (Extensible Markup Language) format. It's compatible with all formula functionality (which can cause workbook formula to 'break' when using older Excel versions) and supports larger sheets than XLS (1,048,576 rows and 16,384 columns) but does not permit the use of VBA macros. The file size of a workbook is smaller when saved as XLSX instead of XLS - whilst storage tends not to be an issue these days, this could be important when trying to email files and stay within a corporate environment's attachment size limit.

XLSX is an 'open' file format which means it's more likely to be read correctly by other spreadsheet software. A workbook saved in the XLSX format is in fact a collection of text files - if you change the file extension from XLSX to ZIP (do this only on a copy of your workbook!) it can be opened in a ZIP file reader to view the internal file structure. I used this 'feature' once to identify which sheet in a workbook was causing it to take far longer than necessary to open: By viewing the text files I could see that one worksheet was significantly larger in size than the others yet looked identical in Excel. It transpired that millions of empty cells had formatting applied - a quick fix when you know where to look!

XLSX Strict - the 'even more compliant' file type. This appears in the Excel file type list as "Strict Open XML Spreadsheet (*.xlsx)" and, as the name would suggest, it complies more strictly to the Open Document standards. It isn't compatible with some of Excels newer and unique features and therefore not widely used.

XLSM - the macro compatible file type. Identical to the XLSX file format but permits the use of VBA macros. Users can identify from the file extension that macro code is embedded and take any necessary security precautions when opening/using the workbook.

XLSB - the latest binary file type. File sizes are even smaller than XLSX and there are also considerable speed gains in opening and saving binary files, compared to the XML formats, when using large and complex workbooks. Functionality is the same as the XLSM file format, since VBA macros can be embedded, so precautions must be taken as the file extension will not indicate it contains macros.

ODS - the OpenDocument Spreadsheet file type. Use this format only if you require seamless interoperability with open source spreadsheet software such as LibreOffice and OpenOffice as there are differences between ODS and XLSX which cause compatibility issues with newer Excel functions and features.

My preferred choice is to use XLSB because of the speed and file size benefits. The only downsides are compatibility with other spreadsheet software (unlikely in most corporate environments) and the precautions that must be taken with VBA macro code. From Excel 2007 onwards the default file type is XLSX but this can be easily changed - in Excel 365 for example, choose "File > Options > Save" and select your preferred default.

"Upload Failed.Error: No file chosen.Your file should have the .xls or .xlsx file extension because Ona uses XLS Forms to create forms..." (as you can see in the print screen attached).This happened to me the first time with the excel file saved as Windows 2010 version of excel. So, I tried uploading the excel file saved as Windows 97-2003 compatibility version of excel. This worked the first time, but neither versions of excel are working for me now.Can you please help me upload the excel file?Thanks very much!