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.

Container field doesn't always display images?

Featured Replies

  • Newbies

I have a filemaker 6 database file called "Drawings". Each record represents one architectural drawing, using a "Picture" container field to store the picture. The container field stores a reference ("Store only a reference to the file") to a .jpg picture file, not the picture file itself.

The container field diplays the picture fine immediately after it is added. However, at some point (usually days later), it will stop displaying, showing the "Could not draw picture file" error message.

- The source picture files are not being renamed, deleted, or moved in any way.

- The problem occurs whether the database is hosted via FileMaker server, or accessed locally using FileMaker client (in which case the picture files are local as well, for testing purposes).

Here's the big, but confusing clue:

- The picture files are organized into job folders, such as //server/public/kia, //server/public/toyota, etc. If all picture references for kia and toytota are broken, and I manually reconnect a picture for toyota, the other toyota pictures will also suddenly display properly as well - but kia pictures remain broken. But ONLY on the machine which reconnected it. Other clients can see only the one picture which was manually reconnected.

That leads me to believe the reference info in the broken container fields is actually valid, since it can be tricked into displaying properly again without reconnecting the link.

Any ideas?

Kurt

The volume holding the images must be available (mounted) *before* opening the database.

  • Author
  • Newbies

The volume holding the images must be available (mounted) *before* opening the database.

Hmmm, well I've tried keeping the pictures folder open on my desktop - just to be sure I have access to that folder - and it still fails.

I've also moved the pictures folder to the same machine as the client (filemaker files and pictures folder on same drive) - that fails too.

Are there any known problems with the length of pathnames? Mine aren't very long, normally something like serverpublicdrawingstoyotatoyotaA1.jpg

  • 8 years later...
  • Newbies

Hi, Did you ever find a solution?

I get the same error "couldnot draw the picture" when scanning and saving the image in "photo" container field. However, if i restart the solution picture comes up fine.

_

Pratik C

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.