Brooks

iPoint is a rapidly growing company that provides a business operations platform for service companies and software for alternative animal therapies practitioners. We utilize Filemaker as the core database and interface but leverage many additional web services to enhance the product. Check out our primary offering at iPointSolutions.net. We need an experienced Filemaker developer who enjoys a relaxed work-from-home environment. Our ideal candidate must be accountable and self-motivated and comfortable working independently on big projects. The individual we hire must be current on modern design and development principles. iPoint is designed to work like a modern SAAS, not an old FileMaker database. You must be creative and show examples of past work that clearly displays your design and scripting talent. In addition to Filemaker skills, you must be well-versed with javascript, RESTful, JSON, and Filemaker Server management. We promote an encouraging and supportive culture and only want people who thrive on positivity and challenges. We do not have high-pressure deadlines and long working hours. If you have what it takes we want to hear from you. Email us your resume at jobs@ipointsolutions.net

This is an old post, but port 443 is probably not open which will cause this behavior.

Not sure if this would help you but I got around this by using a line with the hidden criteria set. This is only good for a fixed row of text.

Fixed it right away.

Just me 2 cents on this but I had the very same problem. Fms12 was fine moved to fms13 and scripts would hang and kill the whole fms engine. I run a batch of scripts in multiple files every 3 minutes and they would run fine for hours or days and then Randomly lock up and kill the fms server. My solution was to deploy a vm client on the server with another fms instance using my developer server license and then Hosted a single fmp12 file that then ran the ots in the main files hosted on the host machine. I run a single ots every 3 minutes on the vm server file that opens all the files on the main host and run the real ots script in each of the main files sequentially. Been running for 2 months without a problem now.

You just need to use external container storage then. http://help.filemaker.com/app/answers/detail/a_id/10244/~/storing-container-field-data-externally

I'm not following your explanation, but a few thousand pictures is not that large if you keep the sizes in check. Use the get thumbnail step to resize them to 2000 x 2000 then keep daily backups of your filemaker solution. Then use a 3rd party backup to keep a copy of your backup ( not your live file! ) everything will then Be redundant 2 levels deep.

I had this issue as well until I upgraded to fms13.

Not sure what result you are after, but once a case function evaluates true it stops evaluation. If you need each of those conditions to evaluate each one should reside in its own case or if statement.

I have extensive experience with both. The performance gains having a data separation model in a hosted environment is negligible at best and not worth the complexity. If you’re going hosted, stick with a single file solution.

Never Mind. It wasn’t so hard. I just used autohotkey to make a script that waits 10 seconds and sends the return key script, and called it with the send command script right before opening the local file. However if someone knows of a built in way please still share!

Hoping there is a solution to this. I host my vertical market solution on my own servers for my clients and I run updates once a month. I have built an update engine that backs up, closes file, takes the file off the server, runs an import process, saves as compacted and then puts new file back in the hosted directory and opens it. This is all automated except for 1 issue. I get the pop up dialog from FMPA that file can not be shared because another user is sharing . This is because I am running on the same machine as the FMSA 13, which I need to do because Im using the command line to control the server for this process. Is there a way to disable the sharing check on the FMPA to stop the message? OR is there a way the automatically acknowledge the message through a script? My thoughts were some sort of windows script that could be called just before opening the files, but wanted to check here before I going down this road.

They are tied to the window not the layout. If you want to stop the on timer script you set it again with an interval of blank using double quotation marks

When you set an on timer script you set hour many seconds are between each execution. So set the script timer for 3600 seconds and the script it calls very 3600 seconds checks for the time and if 3:00 continue.

It is possible. Run the on timer script every hour checking for the time. Wrap your perform script in an If time =3:00