Terra Software

Just a Sunday in YYC taking extra time to insure projects and ventures are flowing and growing👍
-
Business, data mining, marketing and digital workflow issues problem solver!
-
-

Abundance in today’s business world requires real partners and loyal allies. It requires innovative workflow automation and rapid deployment with no hassles or BS. Today’s business environment requires rapid results and to be able to look forward and utilize all tech, media, resources and establish local and global allies.
-
Engage me in what your challenge is and I will bring solutions to the table. I love a damn good challenge.. bring it 💪😎👍🔥
-
Contact me and let’s talk.
-
-

Great thing about FileMaker is that you can absolutely rapid deploy a solution. Currently working on revamping an online timesheet solution for a landscaping company client. The solution has been operational for 7 years. We just upgraded them to FileMaker 18 and doing some quick optimization from the old Instant Web Publishing into WebDirect. Modernization the interface and optimizing for standard cell phone usage. We love working with our clients and we love delivering great solutions in FileMaker Pro.

Contact us today [email protected] or 403-246-8922

Free FileMaker Hosting, Client and server for any client spending $2400 Canadian or more in a year with Terra Software.

Taking on new projects, come challenge us!

http://www.terrasoftware.com

FileMaker Pro - Calgary, Edmonton & Vancouver -Terra Software Terra Software is the FileMaker Pro developer, hosting & support firm located in Calgary & Edmonton Alberta, Canada - serving clients globally.

Something to consider when coding for networks that might have stability issues. Make sure you check that the record ID for a new record is truly unique.

You might think huh ? FileMaker makes the record unique, this is true but also not true in an environment that has network anomalies. I have seen first hand where a record is given a serial record ID that already exists even though it is a serial value assignment to the field. This is due to some sort of network communication hiccup. Somehow it causes FileMaker to trip and allows it to apply the unique previously used and existing ID.

Solve the problem ?
Well after quizzing FileMaker Inc and getting no where the simple solution came up. Upon record creation during the script run, check via a self relationship using the record ID check for a count of greater than 0. If the count is > 0 delete the record and immediately create a new one. Make sure to run a loop and exit if the count in the self relation ship is = 0. This solves the anomaly and prevents the overwriting of older records.

FileMaker does not have the ability to 'Halt Tabbing" at the last field in the Tab Order, so unfortunately the best way to accomplish this is to tag a $$LastTabOrderObject Variable with a script trigger when the last field is touched. The next step is to then assign another script trigger on the first field, this would check the $$LastTabOrderObject Variable and in the scripting jump back to the last field / object.

FileMaker Go... Perfect for visual inventory management