• Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About sfpx

  • Rank

Profile Information

  • Gender
    Not Telling

FIleMaker Profile

  • FM Application
    13 Advanced
  • Platform
    Mac OS X Lion
  • Skill Level

Recent Profile Visitors

1,825 profile views
  1. Thanks for this. Got this error message this morning too. I removed the newly added table from the config and it solved the problem. It appears fmphost does not have this 2.6009 version (the version is 2.6) We really need to upgrade to v3 !
  2. Thanks. We will update in the next few weeks. Meanwhile I will work on an alternative way to get what I want by adding a new synced table.
  3. What I'm trying to do is to update some field with the result of a calculation. This update must be the last action since the calculation depends on related records that may have been updated, deleted or added inside the same sync. Of course I could achieve what I want by launching 2 consecutive syncs like this 1.Sync 2.Update records on the device (any field just to force an update on the hub) that I want to get new calculated results from the server 3.Sync again (in the A RECORD WAS UPDATED ON THE HUB section..I would add the calculated update) I guess that would work but it would be pretty inefficient.
  4. I tried it and no record was added. It really seems like it's not triggered . In the post-sync hub section Perform Script ["UpdateData"] Simple UpdateData test script Go To Layout ["LayoutOfTestTable"] New Record/Request Set Field [TestTable::afield;"abcd"] Go to Layout [original layout]
  5. I understand that MirrorSync 2.305 is probably no longer supported but we won't update before a few weeks and I have a problem that may be simple. I have added a script in the POST-SYNC HUB ACTIONS section of the MirrorSync customization script but it does not seem to be executed. I am attempting to update a field for a few records on the server. The script is simple and looks like Go To Layout MyTable Replace Field Contents [No dialog;myfield;newcontent] I sync and the MyField values are never modified. Am I missing something ?
  6. I just tried the following in the WillDelete section If Get ( LayoutName ) = "travels" set field[cars::lastdestination, "x"] I deleted a travel on the device and synced. The lastdestination field on the device was changed to "x" ! So the modification is sent back to client. The problem I have now is to modify my calculated field so it ignores the travels that are going to be deleted. Can I write something in the record that is going to be deleted or will it cause a problem ? EDIT Got it to work 1.created ToBeDeleted field in the travels table 2.modified the relation between travels and cars so the ToBeDeleted travels records are ignored 3.In the willdelete section I set the field ToBeDeleted of the travel to 1 and reevaluate the lastdestination
  7. I thought about the willdelete section. I haven't tried it because I assumed that the data would not be sent back to the client. I may try it to see.
  8. Sorry for the vague title. Let's suppose 2 tables Table Travels (travelID , carID, destinationID) Table Cars (carid, lastdestination) What I want is to update the lastdestination field in the table cars each time a travel is deleted. What I tried is 1.When a travel is deleted on the phone, I update the car modification time stamp to make sure it gets synced. 2.In the customization script in the "A RECORD WAS UPDATED ON THE HUB" section I added If Get ( LayoutName ) = "cars" set field [lastdestination, last(travels::destinationid)] 3.I deleted the last travel of a car and synced. The lastdestination field was not updated. I guess that this is because the deletion of the travel record is done after the car record update. 4. If I update the car on the device again and sync...then the field gets updated. Any way to achieve what I want to do ? Can I force the car table to be synced last ? P.S. Different users can use the same car. I can not use a calculated field to determine the last position on the device because the other user travels are not on the device.
  9. But was it this particular pause that caused the crashes ? Also if a pause is unsafe I may try other things (freeze window?...go to layout "MirrorSync") but I would prefer that simple pause duration fix. I don't mind having to add it manually. It only takes a few seconds. Also how frequent were the crashes. Were there easily reproducible ? If so, how ?
  10. Turns out the solution is even simpler In the Mirrorsync script #Update/insert records in client from server Set Variable [ $parseError; .....] Set Field [ MirrorSync::status; ..... ] If [ not $$isServer ] Pause/Resume Script [ Duration (seconds): 0 ] End If If I change the duration of this pause from 0 to 0.1 it seems to fix my white screen issue. This remains to be tested more deeply but so far so good.
  11. I was able to eliminate the white screen by modifying the mirrorsync script In the #Update/insert records in client from server section of the script Solution removed as it was not the correct one.
  12. I can replicate the white screen behavior by running this script (any table will do) Script: New Window Refresh Window Freeze Window Go to Layout Test loop Set Variable $1=$i+1 New Record Exit loop if $i=2000 End loop Close Window I tested this script on an new database with only this table On Filemaker Pro on Mac you are getting a black screen for a second or so. On Filemaker Go you get a white screen for the duration of the loop. If you add a Pause Script 0.1 second Just before "Freeze Window" it fixes the problem. I also noticed that the white screen on my syncs always happen after the first batch has been written. If you have any idea on what I could try. I tried to add a pause script in the Mirror Sync Layout onLayoutEnter but it didn't eliminate the white screen. I presume it has to be added inside the mirrorsync script.
  13. That's funny because I was just thinking about that. I may add an empty container to sync for those tables and see if that fixes my problem. Thanks for the quick reply Jesse
  14. I think that happens with small tables that are long to write (because of the database structure more than the actual size of data) For example, my large table seems to be written in batches of 25 records while the tables that give me the white screen seem to be written in batches of 250 records. Not too sure about this...this was deduced by looking at the config utility while syncing.