IWP in linked files

[Alex_Henderson]

I have a problem that's bugging me. I have a large database, some of which is sensitive and I don't want the whole company to view it. Other tables are public knowledge, and I want users to be able to see the contents using IWP. Obviously, I don't want them to browse the entire database, so I have created a separate file with IWP enabled. To keep data integrity, this second file contains no data, but only the layout and scripts - it pulls all its data from the relevant tables in the master file. This all works perfectly over FMNET but when you connect over IWP you get "database not open" and it displays no records. Has anyone come across this before? IWP on the master file works fine, but I don't want that - I only want FMNET on that file and IWP on the linked file. I'm running FileMaker Server Advanced 7 on Win 2003 with Mac & Windows clients.

Thanks

Alex

[Alex_Henderson]

OK - slight update. I've found I got my file references screwed up. When I got that sorted out, I COULD see the data through IWP but only when I had IWP enabled on the master file. If anyone can think of a way of accessing the data without allowing users to see the master file through IWP I'd be really grateful

[John Sindelar]

Assign the fmiwp extended privilege to only one of the Privilege Sets in your file, making sure this Privilege Set has only the limited access to the tables you want to share over IWP. In this way, the other, more robust accounts in that file will only have fmnet access.

[Alex_Henderson]

It's a start, but really I don't want guest users to be able to browse the master file at all.

I think what I should have done is set the master file to have no layouts, so it is impossible to browse over IWP, then make two front-end files, one with IWP enabled, but only pointing to the public tables, and the other will full access to all the sensitive data, but with IWP disabled.

Hindsight is a wonderful gift... I'm not sure I can be bothered to re-engineer the entire project this way though!

Thanks for your input though.