Runtime Application Importing

[marty1452]

I have an application with multiple related files. I'm having difficulties with the importing. When I define an import in the FP5 file, it works great. After binding it to a runtime application, it doesn't work at all. I get dialog asking where the file is located. After selecting the appropriate file, the dialog goes away, it appears to be importing records, but when it's complete, the records did not import.

Has anyone had any experience in defining imports for a runtime app. My concerns are individuals using the application may have assigned a directory on their own when installing the program. I've played with checking and un-checking "relative path" when defining an import. I've tried defining the import forcing the user to pick the correct file, (not my preferred soluton anyway).

Any ideas?

FMP 6 Developer version

Marty

 

[marty1452]

After further trouble shooting, I've discovered additional info that may help track down this problem.

The file is password protected. Logged on as the administrator in the FP5 file, the import works fine. It doesn't work if I opt for the normal user logon. This would explain why the runtime doesn't work, but not why the import quits working with a user logon.

I have discovered the problem. I had a field included in the import script that the normal user does not have permission to access.

I would still like some feed back regarding the "save relative path" or not. What is my best option for the least user interaction.

Thanks

Marty