![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
An interesting dilemna. I have designed a solution that allows a group of individuals to check a central filemaker server over the internet in order to download updated files. It works fine, but causes a problem when they are not connected to the network, in that the relationship i have created between the solution and the IP address of the server comes up as not found and asks them to find the file!!! Is there a way to switch this process off, so that if filemaker cannot see the file it doesnt try, or a way to make the relationship periodic so that only when you want to make the remote link does it look for it? |
#3
| |||
| |||
|
|
In article <1131953995.078224.132390 (AT) f14g2000cwb (DOT) googlegroups.com>, dp (AT) ewitness (DOT) co.uk says... An interesting dilemna. I have designed a solution that allows a group of individuals to check a central filemaker server over the internet in order to download updated files. It works fine, but causes a problem when they are not connected to the network, in that the relationship i have created between the solution and the IP address of the server comes up as not found and asks them to find the file!!! Is there a way to switch this process off, so that if filemaker cannot see the file it doesnt try, or a way to make the relationship periodic so that only when you want to make the remote link does it look for it? Provided you do not "utilize" the remote file, filemaker won't try to open it. By "utilize" I mean, there must be no visible fields or script steps that reference or rely on it. As soon as filemaker is forced to evaluate anything that refers to the remote file it will try to open it, in order to complete the action. Build your solution so that by default, none of the functions or layouts rely on that relationship, write a script to handle opening the remote file, and only allow them to access layouts / scripts that refer to the remote file after it has been opened. I haven't personally tried this with FM7/8, but have a couple FM3/4 and 5/6 deployments that work this way, and work well. Good luck, Dave |
![]() |
| Thread Tools | |
| Display Modes | |
| |