bluewhaleCA
MIS
Hi.
Our company has been running, and growing almost completely dependent upon, Filemaker. We started with version 6 and are on version 10 right now. We have one staff member who spends ~ 60% of their time or more on FM.
A FM shoppe that we hire when we need help recently suggested that there are 'known' things for a Windows admin to do to help ensure FM Server runs properly. Could anybody point me toward such? I can find links to specific topics like running FM server on 64 bit Windows, but no general guidelines ( as opposed to running it on OS X ).
Our other problem is thorny. After X years of using FM and speaking to FM support half a dozen times a year we were advised that page 157 of the FM Pro manual states you should not share FM databases out to the LAN from the LAN. Instead you should open and share the databases out locally, at the console. FM server appeared to be corrupting half a dozen to a dozen databases each night when the built in backup program took the files off line then brought them back up after backing them up. We stopped using the Server version because of this.
Now we THINK the databases were probably quite damaged already, prior to buying the Server version ( we have two licenses for server now ).
1: when sharing from the Pro version is this really a known / significant issue?
2: Does the same prohibition apply to files on a FM Server which are accessed across the LAN instead of being shared at the admin console/portal?
Before we can take a 'last' shot at cleaning up the damaged databases I'd like to be reasonably sure of how FM should be set up: either as shared files from a Pro installation or as an FM Server.
At the moment we have dedicated a workstation to running and sharing out the files from a Pro 10 install. We log on locally and share the files from that console. But would love to get back to using FM Server if we can.
Many, Many Thanks.
Paul
Our company has been running, and growing almost completely dependent upon, Filemaker. We started with version 6 and are on version 10 right now. We have one staff member who spends ~ 60% of their time or more on FM.
A FM shoppe that we hire when we need help recently suggested that there are 'known' things for a Windows admin to do to help ensure FM Server runs properly. Could anybody point me toward such? I can find links to specific topics like running FM server on 64 bit Windows, but no general guidelines ( as opposed to running it on OS X ).
Our other problem is thorny. After X years of using FM and speaking to FM support half a dozen times a year we were advised that page 157 of the FM Pro manual states you should not share FM databases out to the LAN from the LAN. Instead you should open and share the databases out locally, at the console. FM server appeared to be corrupting half a dozen to a dozen databases each night when the built in backup program took the files off line then brought them back up after backing them up. We stopped using the Server version because of this.
Now we THINK the databases were probably quite damaged already, prior to buying the Server version ( we have two licenses for server now ).
1: when sharing from the Pro version is this really a known / significant issue?
2: Does the same prohibition apply to files on a FM Server which are accessed across the LAN instead of being shared at the admin console/portal?
Before we can take a 'last' shot at cleaning up the damaged databases I'd like to be reasonably sure of how FM should be set up: either as shared files from a Pro installation or as an FM Server.
At the moment we have dedicated a workstation to running and sharing out the files from a Pro 10 install. We log on locally and share the files from that console. But would love to get back to using FM Server if we can.
Many, Many Thanks.
Paul