How to identify external file name on Import?

[EllenG]

OK, I have another question regarding Import from a runtime application.

Since I have to allow the user to select the file (if I include a file path in the program, it doesn't find it on the client PC)..

My question is: How can I capture the name of the import file the user has selected so I can verify it is the correct file before running the import script. In this application, there are 2 excel files that the user can import. One is an employee list, the other is a member list. I have to keep these separate and distinct. I setup 2 separate scripts, but since the user has to select the file, I can't control if the user selects the employee file for the member import or vice-versa (even though they are clearly named, it could happen.) Once the file has selected, I would like to be able to verify that the correct file was selected.

There is nothing in the file to identify it (just the Excel file name), and the format of the 2 excel files is identical.

Thanks

[CobaltSky]

Hello Ellen,

To get the level of control you're after, you really should try to get hold of a plug-in such as DialogMagic or Troi File.

Working with native FM commands, the best you can do is:

1. Provide really clear instructions about which file the user is required to select for each script.

2. Provide an undo script that deletes the imported records in case the user has done the wrong thing (as users are apt to do...)

If your users/clients will not pay the price of the plug-in option now, maybe they will be inclined to rethink after their first few brushes with 'disaster'.

[SteveB]

As Ray suggests, a really good choice is the Troi File plugin...it's not expensive at all, and you'll wonder how you did without.

Steve

[EllenG]

Hey, guys. Thanks for your help. I was able to find a way to make it work so that the program always finds the correct import file and the user doesn't have to choose. As long as the relative path stays the same (ie. the import files are always in the correct directory) it seems to work. Although it is a bundled solution ported to another PC, it is only for that one user, so I didn't have to worry about any other platforms.

I will check out Troi for their plug-ins as I do have other problems I have not been able to solve, specifically eliminating the FMP menu bar and eliminate the ability for the user to close files from the window menu... I've tried Dacon for the first, but having problems with it. Also, the developer version is pricey.

Is there any way to get rid of that pesky message when you close an FMP solution "This...was developed using FileMaker Pro 6.." ??

Thanks all.

[SteveB]

There is, but you'd violate your FM license.

Steve