I usually work in OSX and usually just drop into Parallels/WIndows to compile a Windows version of my app. This has worked extremely well; until I got to the Windows portion of my Import script.

I use 360Works Select File() function to get the path. The variable $$Path looks like this:

"filewin:/"&$$Volume&$$SelectImportFile

The resulting 'created' drive/path/file looks like this:

I have tried all kinds of combinations of $$Volume (no $$volume) etc and even tried to hard code $$Path to be as specified above. Import will not recognize the file path and name! grrrrr

I am exhausted from trying to find the 'right' syntax for this import problem. If you have any insight, I surely would apprreciate it.

Regards

Ron

Yes, the cross-platform file specification problem is one of the worst aspects of FileMaker. Here's a technique I use often:

Place an Import Records [ ] statment in your script.

Specify data source = File ... to open a Specify File dialog

Add File ... and select a file from the same directory as will exist at runtime

Observe/capture the displayed File Path that results from your selection

(In Windows, all slashes have to be forward slashes ... "/")

The remaining challenge, then, is to duplicate the path character string in your variable. On Export Records, for example, you can enter a hybrid string, like filewin::/$$CalcdPath right in the Specify File dialog. (But I vaguely recall there are a few featues that don't accept variables in paths.)

And even though variables can be used for most file references, I've never seen a precise statement of the syntax rules. In past years, I've found specific topics on these forums that have helped me figure these things out ... but I'm sorry I don't have any of them noted.

HTH