Running FMP Developer v5.5, a compiled solution can't import directly from Excel -- any version of Excel, apparently.

Is this supposed to be that way? Or am I missing something?

BTW, this appears to be true on both Mac & Windows runtime versions.

I had a problem on Windows platform importing...had to do with FM not changing extension on a kiosk from .FP5 to my own. Is your runtime using your own extension or FP5?

Steve

I'm using my own extension, and letting FMP Dev make sure all the extension stuff is consistent.

The extension thing is interesting, but that shouldn't make a different on a Mac -- and I can't import Excel data even on a Mac.

Well having my own extention created a problem on windows. FM Developer has, not surprisingly, BUGS. Even if Macs don't use extentions, and they are on the file names for consistency, Developer might screw them up. I assume the export works fine when you're not doing a runtime?

It looks like there are system files for Windows and extensions for the MAC that need to be copied to the root level of runtime solution folder. Look in Filemaker Developer 5.5Developer ToolRuntime Files

Yeah, I've got all of those supporting files included in the folder with the solution files (I know I have them all, 'cause I've checked each one against the list in the manual). It's a good guess, but that ain't it.

Any other ideas?

I did some testing and found that if the file to be imported was in any other folder than the solution folder, I would get a file not found error. I could still import the file by selecting it. When the import file is in the solution folder, it imports without error or intervention. I am using 5.5v2 Dev on Win 2000 Pro.