Jump to content

ctmorrison

Newbies
  • Content Count

    3
  • Joined

  • Last visited

Community Reputation

0 Neutral

About ctmorrison

  • Rank
    newbie
  • Birthday 08/01/1952

Profile Information

  • Gender
    Male
  • Location
    Wilmington, NC
  1. I've added commits and flush cache to several places to try and mitigate the problem. However, now that we have more users in the field (about 7), we're seeing this on a daily basis. It has become very frustrating for our technicians. Furthermore, we're seeing other anomalies, such as script triggers not working. I'm now wondering if it's related to our hosting company, who shall remain nameless. However, their pricing was very attractive (aka "cheap") and I'm wondering if our server is starving for resources. We may consider a more expensive hosting company as an alternative.
  2. Has any progress been made on this issue. We recently deployed a solution (work orders for field technicians) and we're frequently getting this error, but with no consistent behavior. We're really struggling to find the cause/solution.
  3. I was pulling my hair out earlier due to a problem with FileMaker Go 13.0.2 on my iPhone 5S (updated OS). I'm running it against a FileMaker 13 server hosted at FileMakerProHosting.com and developed the database with FileMaker Pro 13 Advanced. I have a simple layout for updating a table. On the iPhone, I would click on a field and modify the contents and then go to another record and do the same (List view). If I went back to the original record and tried to modify the field, again, I would get the subject message. Actually, if I went to any record, I got the same message. This would NOT occur on FileMaker Pro 13 Advanced on my Mac. Nor would it happen on my iPad running FileMaker Go 13.0.2 (same version). The problem seems to be unique to the iPhone. I also noticed that my Mac and iPad were not getting any of the field updates I was able to make on the iPhone prior to the error appearing. This makes me think FileMaker Go was in some funky state and not pushing updates--it thought the field was still in the midst of a change. What I do recall is that earlier I had become interested in learning how well Siri would work to enter data into a field. This may or may not have anything to do with the issue surfacing. I have tried using Siri on my iPad and experienced no problems with this same layout. If I logged the iPhone out of the database and reconnected, I would have the same experience. It seems I can update one record, but when I go to another, the problem seemed to surface. Note--the Layout is set to "Save record changes automatically". I tried adding a script trigger to force a commit when leaving the field, but without any benefit. I then tried powering down/up the iPhone and that seems to have fixed the issue. I don't know how to report this to FileMaker, but I do know from other threads that others have experienced this same issue. Any guidance would be greatly appreciated. We're close to putting this system in the field to manage all of our service techs and I'm a bit anxious the problem will surface, again.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.