![]() | |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Hello everyone, this is my first post. I have filemaker pro 10 and I use it like a server. One mac open everything and the others are "Opening remote" to it. So now I have one user who should not modify files for now (they are really many). I've seen the possibility to set up an access set for every file, but I can't do it for every single file. Isn't there a possibility to do it globally? |
#3
| |||
| |||
|
|
There is no way to set access privileges for many files globally. Why do you need so many files? |
#4
| |||
| |||
|
|
Well because they work on at least 20 files which have interconnections. Not even possible through scripting? Maybe I could let that user open directly the .fp7 files on a shared read only volume. It shouldn't give problems if it's read only, am I wrong? |
#5
| |||
| |||
|
|
On 21 Set, 10:41, Jens Teich <spamt... (AT) jensteich (DOT) de> wrote: There is no way to set access privileges for many files globally. Why do you need so many files? Well because they work on at least 20 files which have interconnections. Not even possible through scripting? Maybe I could let that user open directly the .fp7 files on a shared read only volume. It shouldn't give problems if it's read only, am I wrong? |
#6
| |||
| |||
|
|
Why so many files? Ever since FM7, you can have many tables in one file. This greatly simplifies security and reliability. I suggest you rework your solution to combine the several files into one multi-table solution. That takes a little time and effort up front, but will pay dividends in reduced trouble in the future. |

#7
| |||
| |||
|
|
Hello everyone, this is my first post. I have filemaker pro 10 and I use it like a server. One mac open everything and the others are "Opening remote" to it. So now I have one user who should not modify files for now (they are really many). I've seen the possibility to set up an access set for every file, but I can't do it for every single file. Isn't there a possibility to do it globally? |
#8
| |||
| |||
|
|
You can do what I did from FM3 to 6 : create a new 'Open.fp7' file with no record and one script in which you have an 'Open all' script, where you list the opening of each file. Then you create an other 'OpenRemote.fp7' file with no record and one script in which you have an 'Open' script, where you 'Open Remote' the Hosted 'Open.fp7' file. Now on each user machine you copy that 'OpenRemote.fp7' (and call it the way you want) and you open it and by hand you adjust the proper address of the remote 'Open.fp7' file. The user then launches that 'OpenRemote.fp7' file with his local copy of FM10. I'll send you in private a copy of the one I regularly use in FM6. Remi-Noel |
)
#9
| |||
| |||
|
|
On 21 Set, 15:44, "Remi-Noel Menegaux" <rnmenegaux AT free.fr> wrote: You can do what I did from FM3 to 6 : create a new 'Open.fp7' file with no record and one script in which you have an 'Open all' script, where you list the opening of each file. Then you create an other 'OpenRemote.fp7' file with no record and one script in which you have an 'Open' script, where you 'Open Remote' the Hosted 'Open.fp7' file. Now on each user machine you copy that 'OpenRemote.fp7' (and call it the way you want) and you open it and by hand you adjust the proper address of the remote 'Open.fp7' file. The user then launches that 'OpenRemote.fp7' file with his local copy of FM10. I'll send you in private a copy of the one I regularly use in FM6. Remi-Noel Thanks a lot but I already have it... (with the same name )But that doesn't solve my problem, I would like to have a read only user... Maybe keeping a different opener for that user that sets itself in readonly mode before opening makes sense? |
#10
| |||
| |||
|
|
On 21 Set, 14:37, Bill <bbcoll... (AT) earthlink (DOT) net> wrote: Why so many files? Ever since FM7, you can have many tables in one file. This greatly simplifies security and reliability. I suggest you rework your solution to combine the several files into one multi-table solution. That takes a little time and effort up front, but will pay dividends in reduced trouble in the future. The files we are working on are there since FM 3 more or less, and not much changed in the meanwhile ![]() And they are pretty much complicated also, with many formats and tons of fields each.. So I suppose combining them is not an option unfortunately! |
![]() |
| Thread Tools | |
| Display Modes | |
| |