Securing My Databse

[Sintax]

I have a database (1 file with 2 tables) which I plan to make available on my website as freeware for others to download (using FM Developer 7). I know I must get familiar with the Accounts & Priviledges section of FM but there are no books out yet for version 7. Here are some questions that I have run into:

1) I have two tables in my database: one holds all the data and things that the user needs to access while the other just holds the "help file". Can I lock down the Help Table so all they can do is view it and not modify the record I made with the instructions for using the program?

2) I want to release this at first as a beta and there for want to put some limitations on the database so after I work out any bugs, the user will need to download the better version. I would really like to do a "5 Entry Max" something or another where the user can only add 5 records to the database. This would allow them to try it out and see if they like it while also noticing any problems that come about.

3) I have my own layout designed with graphic buttons. Some use Scripts and others use "Specify Button". In any case, the user does not need to have access to FM's own navigation menu. Is there a way to make sure they can't access it?

4) They also do not need to access any layouts other then "Browse" and "Search". How do I keep them from accessing the "Layout" and "Previous" screens?

Thanks all! Hope someone out there can help me

Version: Developer v7

Platform: Mac OS X Panther

[Andy Robo]

This is my first time actually answering/helping on FM - I usually ask!!! so pls don't treat my word as gospel - but hey I just sold my very first solution today - so that's positive!

1) I know that in FM6 when you constrain access using passwords and you set the 'try default password' document preference to a blank entry (that's as a setting for a 'no password', password) then all related files - eg. Your help file will open with the same access priviledges as defined for that access - I too have just started working with FMD 7 and in an converted fp5 file in fmd 7 the same result occured -

if you've constructed straight from fmd7 you need to define a 'guest' in 'define accounts & privs'

- once in the privledge sets tab you can edit the guest account...

As for 2) I imagine there could be heaps of ways of doing this - possibly using a global field that inputs the time/date when the user first logs in, and then checks it using a calculation and script every subsquent time they 'log' in - of course they're logging in without 'logging' if you use the example above.

inside an IF (isempty FIELD) statement use a set field - insert current date in an opening script -

the first time the user opens the soln a date will be inserted - in subsquent openings the field will contain the date and will then read a next step - somethign along the lines of -

if (

startDate + 30 > endDate

)

showMessage...

quit

else

...

end if

this is not good scripting - i'm doing it from memory so pls don't quote me

(3) do you mean the 'status area' ? if so the show/hide status area script step will work if you throw it in the opening script.

... for other menu accesses use the accounts and privledges

4) you could delete them right before you've bound your solution!!! or again, use the privledges definitions

Good luck!!!

[Andy Robo]

Oh bugger - sorry didn't read your second point properly and didn't answer it at all did I! Sorry!!

Um, you could use a GET(currentRecordCount) script step - to prevent access when users click a 'new' button... this would be bypassed if NEW RECORD was available from the menu - but you can shut that down using ACCs and Privs... so that might work - embed it in an IF statement.

[Singlequanta]

Have a look at the solution that Vaughn has created. It is located in the FM7 sample files area (i think)

While it might be overkill for your application, his solution has a really good approach and simplifies the use of FM7's internal accounts/etc. I'm sure you could easily reduce it to your needs, while also learning how the new security features work.

SG

[Vaughan]

Thanks for your kind words about the security demo...

"... simplifies the use of FM7's internal accounts/etc."

That wasn't really its intention... it mainly provides an alternative interface to the Accounts and Privileges commands that can be used by users without [Full Access]. It also provides a "groups" feature for the login accounts.

The Define Accounts and Privileges in FMP 7 is easier to use than Passwords and Groups in earlier versions. Much easier. There is more to learn too but it makes much more sense and is more intuitive.

[Chuck]

Could someone post a link to Vaughan's security demo in FM7? I'd really love to take a look at it but haven't been able to locate it.

Thanks,

Chuck