I have a filemaker runtime solution that I have been working with for the better part of a year now. It is operating commercially on 40 computers. Of course, over the year it has evolved as all solutions do. Recently I employed an idea that I've had for a while to incorporate images in a sort of "screensaver" kind of operation. Part of the requirement was having fairly up-to-date access to the image files, in this case a series of .jpg and .gifs.

All 40 computers have a shared network drive where the images are stored.

I instigated this "upgrade" by using a plugin from TroiAutomastering. Initially, I used the plugin to just display the image in a global container field, and every 20 seconds or so to get the next image and display it.

However, much to my chargrin the solution blew up after running for an undeterminable period of time - i.e. in some cases it ran for hours in others it ran for minutes with no descernable pattern.

In trouble shooting this I thought it may have been an issue with the plugin, so I created a secondary database and a simple relationship. The second DB contained the images directly inside a container, and a simple indexing scheme allowed me to display those on the parent and to update the image by changing the index.

Alas... the problem still occurs only not nearly as frequently. Instead of blowing up every XXX minutes it now blows up with 1/10th the frequency.

Now I have messed around with this to the point of starting a scratch sample file with no other functionality/fields/scripts other than something that displays a JPG every 10 seconds from either a repeating container or a referenced relationship.

Invariably it **eventually** crashes - either as a runtime solution or as an FM 5, 5.5, or FM6 run database.

I'm at my wits end. Has anyone else encountered this sort of problem using repeatedly refreshed images?

Cheers!

Platform?

What plugin are you using?

-Stanley

Solution is running on XP, both Home Edition and Professional Edition (not that there is much difference between the two)

The plugin i am using is from TroiAutomastering called TroiFile www.troi.com (they make really great plugins)

Although whilst debugging this issue, I eventually whittled the solution down to nothing more than two files with hardwired GIF/JPGs in them (i.e. didn not use the plug in at all) and the thing still blows up after a given period of time.

Steve

It can be bad compression/decompression in picture.

It can be anything