![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Hi All, I have until recently had FMP7 application shared across 5 users on a small PTP network with the database residing on one XP box on which the Host logged in to open the database and the others shared it Remotely. So far "stock standard" small installation with no problems. Later on we installed a Win2000 File Server into the n/w and my superiors wanted the FMP7 db to reside on this FS (for backup etc) and not residing any more on one of the Client Machines 1. I moved the db from the client box to the Win2000 FS 2. I can host the db from any client by browsing the n/w to the server and opening the db directly 3. Other users then connect Remotely to the listed remote address My questions / comments are 1. All literature, comments so far say "DON'T DO THIS" 2. I have never had a stability or any other problem in this mode 3. In fact FMP7 is very accommodating in that it always provides the Remote Connection address 4. I have crashed the hosting node to test it and then reconnected again - no problems 5. I have no problems with Record Locking or other forms of data sharing 6. The Remote Host always keeps control and can message to all remote users ok 7. The FS Server provides a reliable and backed up platform for the database 8. In fact the overall system seems faster by having the data reside on a fast File Server 9. What problems am I supposed to be experiencing in doing this "frowned upon" setup Best Regards Ron H. |
#3
| ||||||||||||
| ||||||||||||
|
|
Hi All, I have until recently had FMP7 application shared across 5 users on a small PTP network with the database residing on one XP box on which the Host logged in to open the database and the others shared it Remotely. So far "stock standard" small installation with no problems. Later on we installed a Win2000 File Server into the n/w and my superiors wanted the FMP7 db to reside on this FS (for backup etc) and not residing any more on one of the Client Machines 1. I moved the db from the client box to the Win2000 FS |
|
2. I can host the db from any client by browsing the n/w to the server and opening the db directly |
|
3. Other users then connect Remotely to the listed remote address |
|
My questions / comments are 1. All literature, comments so far say "DON'T DO THIS" |
|
2. I have never had a stability or any other problem in this mode |
|
3. In fact FMP7 is very accommodating in that it always provides the Remote Connection address |
|
4. I have crashed the hosting node to test it and then reconnected again - no problems |

|
5. I have no problems with Record Locking or other forms of data sharing |
|
6. The Remote Host always keeps control and can message to all remote users ok |
|
7. The FS Server provides a reliable and backed up platform for the database |
|
8. In fact the overall system seems faster by having the data reside on a fast File Server |

|
9. What problems am I supposed to be experiencing in doing this "frowned upon" setup |
#4
| |||
| |||
|
|
7. The FS Server provides a reliable and backed up platform for the database |

#5
| |||
| |||
|
|
Hi All, I have until recently had FMP7 application shared across 5 users on a small PTP network with the database residing on one XP box on which the Host logged in to open the database and the others shared it Remotely. So far "stock standard" small installation with no problems. Later on we installed a Win2000 File Server into the n/w and my superiors wanted the FMP7 db to reside on this FS (for backup etc) and not residing any more on one of the Client Machines 1. I moved the db from the client box to the Win2000 FS 2. I can host the db from any client by browsing the n/w to the server and opening the db directly 3. Other users then connect Remotely to the listed remote address My questions / comments are 1. All literature, comments so far say "DON'T DO THIS" 2. I have never had a stability or any other problem in this mode 3. In fact FMP7 is very accommodating in that it always provides the Remote Connection address 4. I have crashed the hosting node to test it and then reconnected again - no problems 5. I have no problems with Record Locking or other forms of data sharing 6. The Remote Host always keeps control and can message to all remote users ok 7. The FS Server provides a reliable and backed up platform for the database 8. In fact the overall system seems faster by having the data reside on a fast File Server 9. What problems am I supposed to be experiencing in doing this "frowned upon" setup Best Regards Ron H. |
![]() |
| Thread Tools | |
| Display Modes | |
| |