Has anyone found what XLSX versions are supported for an FM19 import? I get a strange message, but can't find any information about supported versions. But maybe the error is simply misleading.
(I can try to create the screenshot in english if it helps).
The output is from a 3rd party software.
BTW: Importing it via File -> Import Records works with this same file (used it to create the target table in the first place).
Opened it with MS Excel, made some change and did "save as...". Same result.
I have a colleague, who, within the last year, ran into a similar message about "wrong Excel version" when doing an import. My suspicion was always that the error message was incorrect, and that he was actually running into some sort of condition whereby FMP just wasn't able to find or access the file at the target path. I just pinged him to see if he could remind me of the resolution, but he does not recall.
I mention this because some of the symptoms mentioned in this thread also suggest to me that it could be more a question about whether the file can be located/accessed during the import records script step, rather than a conflict with a file version. No guarantees, though -- this is just speculation, and not with a whole lot of substantiation.
If none of these suggestions solve the problem, I'd be inclined to take a 365-generated Excel file that you can verify "works" in this situation and compare it using a byte editor to an "identical" file generated by the third-party software. These XLSX, DOCX, PPTX files are all basically zip files, but perhaps the issue is right in the file header.
It works on 2 computers (Ventura 13.5.2 and Ventura 13.6), both FM19 and FM20.
It doesn't work on the 3rd computer where I programmed it (Ventura 13.6), both FM19 and FM20.
FileMaker versions are the same on all clients.
I'll stop for the moment, maybe I'll try to compare some library directories.
The libraries look OK, still no idea what goes wrong on computer 3
Changed the script to run on server as intended from the start (PSOS). For this to work, I had to copy the file via script from a "public" server directory to one of the predefined directories (Paths in server-side scripts).
At first, "import records" returned status 0, but imported nothing.
changing the file mode from "--wsrwsr-t" to "-rw-rw-rw-" solved this problem, too. That means, even though FMS had read rights as group, it didn't import anything, but returned OK.