Stopping access to bound solution

[johnrh]

I am writing a standalone application in kiosk mode. Once bound, I need to prevent the user (or anyone else) accessing the data using normal filemaker - or any other program. I know I developer will prevent file and layout amendements but i also need them not to be able to view the data. Am I missing something? Can anybody point me in the right direction?

Many thanks

[Lee Smith]

Huh, you don't wont them to see their own data?

[johnrh]

I do not want them to be able to view the data through clicking separately on the usr file that forms part of the bound solution.

[Lee Smith]

Then point them back to your menu using scripts. In other words, use a startup script in that file that when opens, hides the file and opens the main menu.

HTH

Lee

[Robert Kidd]

I think a bound solution will always open your primary file first, even if another file is double clicked.

BTW.Remember to set your access privileges to prevent importing from your data file

[Lee Smith]

Hi Robert,

I have not bound a solution, so I can't test this, However, I have clicked on a data file (just a few minutes ago) and had it open on top of the main menu (this is a fp3 bound solution, so it could have changed in version 5+ though).

Might be a good idea to have the opening script for this data file go to a blank layout and lock down the navigation menus.

Lee