Skip 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.

Export field data and Nul insertions

Featured Replies

Hi. I've noticed this issue before, but now it's causing problems for me so I figured I'd ask. I'm exporting a single field as a text file from FM11. This file will be used as an .ics calendar file. When I copy/paste the text field into a blank text file, no problem-it's recognized by calendar apps as an ics. If I use the export field function the calendars app won't recognize it. I noticed that the exported file is double the size of the copy/paste file, however both files look the same when opened in a text editor. I opened them in a hex editor and found that Filemaker is exporting the field data with a hex 00/Ascii Nul between every character, hence the doubling in size. This is obviously causing problems for the calendar apps that don't expect these Nul characters. Other than scripting a copy/paste function between filemaker and a text file any advice?

Thanks

edit: A little more on this. If I open the exported file with the nuls and delete all the text in it then put any text back in it manually, the characters all show up with nuls when I open the file in a hex editor. So when FM is exporting to a text file, it seems as though it is doing something to the file itself. I'm on a mac by the way. I haven't had a chance to try in windows.

When you export field contents, the resulting file is UTF-16 encoded - which not all applications know how to handle. Several alternatives exist, for example using AppleScript or a plugin to write directly to the file, or exporting as XML with a suitable XSLT stylesheet.

  • Author

When you export field contents, the resulting file is UTF-16 encoded - which not all applications know how to handle. Several alternatives exist, for example using AppleScript or a plugin to write directly to the file, or exporting as XML with a suitable XSLT stylesheet.

Thanks.

I will give it a go.

  • Author

Thanks. I went with an applescript. Works nicely.

  • 4 weeks later...

Create an account or sign in to comment

Important Information

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

Account

Navigation

Search

Search

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.