AnsweredAssumed Answered

Perfomance of calculated container fields cross-platform

Question asked by jwilson on Jul 23, 2018
Latest reply on Aug 8, 2018 by philmodjunk

I have developed a database on a Mac where each record displays a related jpg image via a calculated container field (imagemac:/Drive/User etc etc).  The images themselves are stored outside of filemaker but locally in a structure of subdirectories, and the calculation works out which one to display, based on other data fields in the record. 


The Database works fine on the Mac and browsing records is reasonably fast.  However when I come use the database on a Windows machine, it is unbelievably slow, taking 20 seconds to display a record.  The Win version is accessing the same images, copied to the local computer and in the same subdirectory structure.  The calculation of the conatiner field accounts for the platform, and on Windows results in imagewin:/C:/User etc etc.


Due to an unfortunate set of circumstances I am stuck using FMP13 - is this the cause of the extreme sloth? Or is there some fundamental constraint when displaying images via calculated container field in Windows?