
ghagen
Members-
Content Count
9 -
Joined
-
Last visited
Community Reputation
0 NeutralAbout ghagen
-
Rank
member
-
This worked, although it required adding a bunch of container fields to my schema. Specifically, what ended up working best was creating a layout (script accessible only) that was connected to a "user" table (because the temporary files might need to be created in a multiuser environment) that had an abstracted link to a document templates table, and another abstracted link to the destination table/record where the resulting file needed to be saved. This let me just refer to the object names without ever changing / losing context. I did discover after much troubleshooting, that appe
-
I have an important application where I build a very large document in optional, themed sections. Currently, my process is to append a template section, make text substitutions against placeholders in each section, and then append another section, until the entire master document is built. However, in practice this means that when I add a new section, Scribedocsubstitute must scan, find, and replace against an increasingly large document - even though only the new (short) section has any replacements to be made. This means that the overall script slows exponentially with each added section.
-
Wim - thank you for taking the time to respond. What you state --- is not clear on the Filemaker website! You probably saved me a bunch of confusion and research.
-
Wow, I guess I'm still waiting on this answer. According to the Filemaker website, server-side plugins are now supported (I saw a youtube video with an earlier comparison page that appeared to say differently). https://www.filemaker.com/products/filemaker-cloud-for-aws/compare.html If anyone has any specific experience with the Scribe plugin on the cloud, I'd really like to know!
-
Followup: This seems to be representative of an issue that appears on OSX from time to time. However, all solutions I tried accomplished nothing. - Removing DBCache - Selectively removing all Filemaker related temporary files and preference files - Running Disk Utility to fix all permissions - Running another repair utility (Cocktail) to run all maintenance scripts and flush virtual memory - Deleting (and recreating) the entire S10 temp directory above again, no luck. Is there a setting in Scribe to create a different name? Because otherwise, Filemaker is working just fine.
-
FM 18 Pro, OSX Catalina, 2019 Imac. I've been working with the Scribe plugin for weeks, having developed many complex and successful scripts. While adding to a script (unrelated to 360Works, I believe), my Filemaker database locked up and had to be restarted. Since then, I have not been able to complete the ScribeDocSaveContainer process. When it reaches that point, the following error is thrown: '"$tmp" could not be created on this disk. Use a different name, make more room on the disk, unlock it or use a different disk'. I have restarted the OS, deleted the entire Filemaker
-
ghagen joined the community
-
Is Scribe fully compatible with Filemaker Cloud?