|
Your continued generosity and support of FMForums is greatly appreciated. |
ejpvi
apprentice
Posts: 135
Post Rank (AVG):
FMP: 10 Advanced
OS: Windows Vista
Skill: Advance
 Tweet This Post!
|
I recently noticed that one of my scripts hasn't been working correctly.
If I run the script manually from a client, it works perfectly.The script involves running through a loop, which copies records to variables, then switches to a different table, creates a new record, and pastes the variables down, then switches back to the layout to continue copying until it reaches the end.
This works perfectly... except when I schedule it to run automatically on the server.
Then it usually only captures half the records, and at some point spits out the error
Error (101) Go-to-Record...
as far a I can tell, there isn't any compatibility issues with the server... but this keeps happening.
Has anyone else had this problem with scripts running improperly on the server?
Thanks!
|
|
|
 bcooney
consultant
Posts: 3617
Loc: New York
Post Rank (AVG):
FMP: 10 Advanced
OS: Cross Platform
Member: TechNet
Skill: Advance
Certified:
    
Tweet This Post!
|
In response to ejpvi
When you loop, FM throws an error when it runs out of records at the Go to Next (Exit at Last). However, you say it only captures half the records. That is odd. I'd look to see that you are in the right context when you set the variables (going back to the right layout and found set? and when you set field.)
The process you describe might be improved as well, but I don't know all the details. An import perhaps? Setting one key and doing lookups?
|
|
Your continued generosity and support of FMForums is greatly appreciated. |
ejpvi
apprentice
Posts: 135
Post Rank (AVG):
FMP: 10 Advanced
OS: Windows Vista
Skill: Advance
Tweet This Post!
|
In response to bcooney
Thank you Bcooney, I can always count on you for a response.
Right before you responded... I finally found a post about Server Side Scripts always spit this error up during loops... so where I was first very concerned, then I was just confused.
Then I realized the reason the records were off, was because of the stupid proprietary system that I was copying records from. It auto-imports from our website the orders. If someone doesn't log in once a day to that system, then it continues to pull orders and assign them to the day it was last logged in (previous day).... hence why, when I was running my script in the middle of the night to pull all orders from previous day... several more orders appeared for the previous day after that, and my system was matching...
So now I just run my server-script closer to afternoon, when someone has definitely logged into the other system, and it works like a charm.
Sometimes working with Filemaker is so much easier than these proprietary systems we pull data from, sometimes you have to pull your hair out to figure out what it is they are doing and why info doesn't match.
Thanks for your time!
|
|
|
03-08-10 12:07 PM - 
03-09-10 12:57 PM - 
