With all of the databsases I create, I include a field called "FINDIT". This field contains a concateneation of the record number the person's name and street address, and other such stuff as might be commonly searched for. I always set this up to be the second script in my active script list (the one that show in the Script menu pop down). These have worked perfectly for years. Suddenly none of these work.

At first I thought "bad keyboard", but changing to a brand new keyboard did not help. Next I tried changing the script to a different position in the list (one that I know is functioning correctly) - no help there. Next I deleted the script, and rewrote with a different name - again no help. Next I took another scrip (which was working just fine in the fourth position of the list) and moved it to the second position - pressing Command 2 produced no results. Finally, I moved the "FINDIT script to position 8, and pressing command 8 did execute the script.

This is more of a nusuance that anything else, But can anyone tell me why this bizzare thing happens?

Um, debugging sucks. First thing to do is revert to your original scripts (get rid of all your test changes). Next, put a show custom dialog in a branch and try out that branch. If you see the custom dialog, you know you are getting to that point in the code -- if not, there is a reason why. Find it. (Probably a syntax change between FMP5 and 6.)

If you can't spot the error with dialogs, print your script out. Then search the help file for each and every script step and function in your script. Make sure they are all there and work the same as you use them.

--

"You can't even throw the game."

My guess would be that particular machine uses some sort of hotkey program which overwrites the Ctrl-# functionality in FileMaker.

hi John,

You show two different versions of FileMaker in your Profile, and your Operating System of 10.3.x, but none for This Post.

Is this the Same Machine, different machine, platform, OS than the one assumed?

I believe that JT has hit upon it, but there might be something else entering into it.

Lee

Sorry to waste anyone's time - this turned out to be a conflict set up by a QuicKeys shortcut. It was supposed to only work in Safari, but it somehow got assigned to All Applications - DOH!