Prompt for password

[Linda Dobinson]

Hello - does anyone know of a way to have a prompt for password? I'm
running server 5. For example, I have a database that our technical support
reps log their calls in. Some calls need to be escalated to a higher level
technician, and we have 3 levels of support. Level 1 techs escalate to
level 2, and level 2 escalated to level 3. I've created a script that
handles the escalation process, but I would like to limit who can run the
script; only a level 2 tech can escalate to level 3 for example. Limiting
the ability to run the script via the access privledges is not an option -
our tech department is open 24X7X365, so having to take the database down to
modify access privlidges doesn't work - I would need to be able to make
changes on the fly.

Does anyone know of a way to prompt for a password to be entered before a
script can be run??? I thought about having the script bring the user to a
password layout where they enter the password into a field, then the script
validates the entry in the field, but the entry is not encrypted and
therefore could be seen by other techs looking at that layout or even
looking over a techs schedule.

Any ideas?

Linda Dobinson
Director of Technical Operations
CP Internet

[John Weinshel]

Not quite sure how you intend to implement any changes if you can't bring
the hosted files down long enough to install changes. There's no way to
write code when the system is running. You can kick everyone else off and
perform most development, but access privilege mods require booting in
Filemaker.

Assuming you get past that hurdle, you can either use the access privileges
to create groups, and test for the group name, using PattenCount() and
Status(CurrentGroups), or build a custom login system, using a separate file
to store users and track their usage, or a combination of both.

Groups need not be hierarchical-- two groups can have the exact same set of
privileges, but just be targeted differently (which would probably suit what
you need). But you've got to be able to get in there and do the work.

--
John Weinshel
Datagrace
Vashon Island, WA
(206) 463-1634
Associate Member, Filemaker Solutions Alliance

"Linda Dobinson" <ldob...@cpinternet.com> wrote in message
news:vj5o8.112$yv4....@newsfeed.slurp.net...

[Paul Bruneau]

John Weinshel wrote:
>
> Not quite sure how you intend to implement any changes if you can't bring
> the hosted files down long enough to install changes. There's no way to
> write code when the system is running. You can kick everyone else off and
> perform most development, but access privilege mods require booting in
> Filemaker.

I'm not sure what you mean here, John. I do all kinds of modifications
with my files up. The only things I can't do are define fields (and even
then, I only take down the one file, edit the fields and then open it
back up, all from the remote server admin.

As for the passwords, if a FM developer is working in house on live
files, like the writer wants to do, the only viable option is to create
one's own password system like John talks about. Forget using FM
passwords in this scenario. I suggest one password that is the master
for all files that only the developer knows, and then one password that
all the users share, with different permissions allowed via scripting in
conjunction with the homegrown security system.

PB

[John Weinshel]

Yes-- that's what I meant (define fields). Just about any kind of login
scheme will require access not allowed on a hosted file.

--
John Weinshel
Datagrace
Vashon Island, WA
(206) 463-1634
Associate Member, Filemaker Solutions Alliance

"Paul Bruneau" <ethica...@mac.com> wrote in message
news:3CA10A2A...@mac.com...

[Shifu]

You can use a text field and a if statement
If field A = Level 1 support
Go to Level Level 2 support
etc