Different Layout for find mode

[damaru]

Hi all,

I am working with Filemaker 7 and one of the main problem I encouter lately is that people are in find mode and dont know about it. They then try to enter new customer information and then freak out on me saying 'It was all there and it all Disapear I didn't don anything wrong'. I try to teach them the find mode but still error are comming in. Is there a way to Put a big red FIND MODE in the middle of the form so my staff dont screw up ? Or somthing like change of color, I feel the dotted line arond the field just is not visible engouh

Thanks

[T-Square]

Off the top of my head, you could create an unstored calculated text field:

cMode:

If (Get(WindowMode) = 1; "FIND MODE"; "")

Placing this on your layout, formatted in a big red font, should serve your purpose.

David

[damaru]

okya iget the idea, so I create a text field in my database, and make it by calculation enter the code you got there and put this field in my layout but all the field become blank when I switch into find mode. I know there is something I dont get.

Thanks for your help

[Ender]

You might also consider dedicated Find layouts. The idea is to have your Finds scripted so that they switch to the Find layout to perform the Find, then switch to a List layout to show the results (or maybe a Form layout if there's only one result). You can then add visual cues to the search fields (like a different colored field background) so that's it's easy to tell that those fields are not the same as the data-entry fields. This way, you can put any fields that might need to be searched in one place, and not worry about users being in the wrong Mode.

[damaru]

yes That was my first take on the project, but it's a 12 table database with tons of layout, the search layout would be quite full, that's why I was looking moore for a simple decoration in whichever layout when I am in find mode... I am keeping on !

Thanks for oyu imput!

[damaru]

I found the lamest way of doing it ! I created a containerfield with a white square, once we get in find mode, the whit squre disapear and at the back I wrote FIND. Really Lame but it works ! Now how do I make a container field to have a image auto entered in there ? Is there a way ?

Thanks

[LaRetta]

Off the top of my head, you could create an unstored calculated text field: cMode: If (Get(WindowMode) = 1; "FIND MODE"; "")

...but all the field become blank when I switch into find mode. I know there is something I dont get.

Calculations don't display in Find Mode. I agree with Mike that dedicated layouts are the safest. Mistaking Find for Browse is a common error. I make the background yellow - all my Users know that if layout is yellow then they are in Find and I TIGHTLY control it so they are never in Browse on this layout. When Users are focusing on their work and jumping around and have customer on phone, they can get distracted. It is worth the investment of design time to properly protect them. You can have several Find layouts (or small windows) - you don't need to put ALL tables/fields on one Find layout. :wink2:

[T-Square]

LaRetta--

I didn't know about that display issue WRT calc fields in Find mode. Thanks for that!

I have done the dedicated find layout route as well. However, I like damaru's workaround because I have found that users often enter Find mode without knowing it using Ctrl/Apple F. [My other keyboard bugaboo is the Ctrl/Apple D, which many users think will delete a record--not duplicate it. But that's a horse of a different color...]

David

[Ender]

C'mon David, you should know better than to let users have access to menu commands. What happens when someone tries "Delete All"?

[T-Square]

Ender--

Maybe I should know better... but I've been lucky enough to work with a small, generally benign (!?!) group of users whose main troubles in this arena are honest mistakes (like the Apple D) rather than actively seeking the Delete All Records option. So, I've never done any locking down of menus, and therefore have no knowledge of those capabilities. My design method has been to put the functionality my users need on screen, and I've found them happy to leave well enough alone with the menus by and large.

David

[Ender]

Sure, it works fine until there's a problem.

I hope you'll rethink this "happy to leave well enough alone" policy. Though it may involve additional buttons to do commands that some users currently use menus or key commands for, locking out the menus is a good measure to take to protect against deliberate or accidendal record creation & deletion, Replace, and untimely Mode changes, any of which could cause issues with later processes. The resulting problems may not even be noticed for days or weeks, by which time it would be a lot more work to clean it up.

If you still wish to provide some menu commands or your users are in love with key commands, you can customize your menus with SecureFM or FM8 Advanced's custom menus.

Now no more talk of 'benign' users who make 'honest mistakes'. We all know you're breeding the next generation of super hackers over there, who'd like nothing better than to screw you out of a job by showing how easy it is insert "The Boss is a Boob" in all the records. Don't give them the pleasure. Secure your files!

[LaRetta]

Well said, Mike. David, you can remove most menu commands through Privileges (it is very easy) and just add a few buttons. The Add 'can' be generic to many tables, just as the Delete or Delete Portal Row can. I use SecureFM to remove menus; I couldn't imagine the wreck our data would be in without these protections.

Users pick up many shortcut commands from many different programs. And even the best-intentioned User can accidently fire this key combination without thinking ... heck, I've done it while working in an unlocked file, and I KNOW better.

[T-Square]

CURSE YOU ENDER!

Once again my plot to take over the WORLD through hidden keyboard shortcuts has been THWARTED BY YOU DO-GOODERS!

I and my evil brethren will have to find ANOTHER WAY to compromise the security of information!!! You haven't heard the LAST OF ME!

MWAH-HA-HA-HA HA!!