Jump to content
View in the app

A better way to browse. Learn more.

FMForums.com

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Possible import with runtime in v3 bug.

Featured Replies

Hello,

I just upgraded to FMD 7 v3 and when I tested my DB in Filemaker everything works great. I then created a runtime to test and the import doesn't work through a script.

I created a script so users can backup and restore their data. I have the script setup so they can either have FM do this automatically with their backup data on drive 'c' or they can do a userselect and select were their backup is located. Basically just removing the file name in the import script. The automatic works fine in both export and import, but when they try to import by user select FM doesn't ask were the file is located it just goes through automatically and doesn't actually import any records. This is strange. If I do a backup with user select file, FM will ask what to name the file, but it won't work with importing.

I then took my file over to my notebook that still has version 2 and created a runtime and the import works flawless.

This has to be some type of bug or change to FM 7v3 when you create the runtime. I can't seem to find it in the readme.

Does anyone have a clue to why this would do this or if they are experiencing the same results?

Any help would be great since I really don't want to go back to v2 if I don't have to, but I just might.

  • Author

Ok, I did some more exploring. My script does not have a specific import file listed, it is blank. When I create the runtime, I opened the .usr file and checked the import script and FM filled in a file name automatically. It used the same filename for all imports (I have 3 for 3 different tables). I can then uncheck the filename in the .usr file import script and then it works fine.

This is really strange. This has to be a bug and one that is really going to drive me crazy since now I have to remember to clear the filename from the import script everytime I make an update and a new runtime file.

Any help on this would be great.

Thanks,

Brad

  • Author

After further review. FM V3 will now auto fill in your import from the last import you designate. I have created a script so that a user can pick whether or not to input a filename and FM V3 will auto fill in the filename once you create the runtime. It will pick the last filename you created. I have now reinstalled and went back to V2 and it works flawless. This really sucks since I will lose out on all the enhancemnents. But it is what it is.

  • Author

I feel like I am talking to myself. Doesn't anyone have any input? Am I crazy? Is there a workaround?

Create an account or sign in to comment

Important Information

By using this site, you agree to our Terms of Use.

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.