Since going from version 2 to 3 of MirrorSync last year we have constantly had MirrorSync crashing the Web Publishing Engine.
Sometimes it says "Error from server: FileMaker XML WPE Web Publishing Engine is not running at <the hosted IP>. Ensure that the WPE is working correctly, and then try this operation again."
But usually it is an Error 10 error. "Error 10 while connecting to http://<the hosted IP>/sync?ping=1&config..."
Early on we made the documented suggested changes for this error, to the connectionTimeout Property in the IIS Manager application. With no noticeable effect.
Most of the time MirrorSync works as expected and does a great job and then clients can't sync and all hell breaks loose.
Do you have any other suggestions for what might be causing this issue?
During the installation of MirrorSync I can not select the spoke database if I select the option to use a separate mobile file.
I get an error message thta MirrorSync can not get the database names (image mirrosync2). However database names are available when I select the hub database (image mirrosync1). When I select the option sync with an emtpy clone or complete copy of the main file I can continue the installtion process.
Any idea why Mirrosync can not find db names for the spoke database?
I've broken a pdf saving script which used to work. The filename itself hasn't changed so I don't think that's the problem (there are no /s for instance) - I'm pretty sure it's the file path and Mac OS re-organising itself to sync with iCloud.
I'm trying to save PDFs to Dropbox and I think that the Dropbox folder on my my has changed location. According to info, the location is /Users/mikekentdavies/Dropbox/KJA Music Library.
The calculation I'm using to set the location variable is below; can anyone see where I'm going wrong? (I've also tried various combinations of filemac: / file: / .. / : etc having read the FM creating file paths webpage.)
"filemac:../Users/mikekentdavies/Dropbox/KJA Music Library/Set Lists/" & Gig::Gig Name & " - " & Gig::Version & " Set List.pdf"
I read that the new 3.01 version does not require Java.
When I run FMPAv16 on my Mac (10.11.6) and use the sample Email database it works just fine and I see nothing related to Java. I had the older v2.12 plugin installed on here and have just updated to v3.01 today.
When I run FMPAv16 on a different Mac (10.11.6) and install the v3.01 plugin (never had the plugin installed on this machine before today) and run the sample database a Java App runs without any windows, Just visible in the lower right dock and its single menu is titled "Java"
Any ideas as to this oddity?
By Mr. B
We are Americans who are a non-profit and have a school for squatter children in the slums of the Philippines and would like to create student attendance database that provides various rewards.
Our goal is to encourage the kids to attend school who otherwise wouldn't and provide them with a reward point type of system. Each day they attend school, they get 5pts. If they remembered to wear their school uniform they get additional 5 pts. At the end of the day or the end of the week, they can use their points and trade them in for rice, milk, things that will help them feed their family, get school supplies etc.
We would like to account for how often they come to track their daily attendance. We are hoping to include other fields that would be helpful to medical assistance, needs, etc.
As of now, we print and laminte, cutout little paper coins we give them and it is a lot of work. We have around 400-600 kids who attend class. Annually we have several large community events where we track the daily attendance during summer of up to 3,000 students who attend. This is all done by hand so a digital type system would really benefit, save time, manpower, and streamline what we are doing.
- track attendance
- reward attendance and such by point system
- can use their student card points at cafeteria for snacks or for extra stuff as incentive to help their families.
If you know of something that would help us, or have some ideas, please let us know.