To whom it may concern:

I need help securing one of my applications. I have a time clock application. I have a button the workers push to punch out for the day, etc. I have this application secure in certain areas no problem. I do have 2 questions. The first question is I have the following program example:

Var VMenu1 as Int
Var VMenu3 as Int
Var VSuccess as INT
Var Vdate as date
Var Vtime as time
   
   
         vMenu3 = @SelectTreeItem("CLOCK!Forms!Search/Update!Clock!Time Clock")
         VSuccess = @SelectTreeItem("Search Menu!Clear Form (F3)")      
     Vtime = @time
         Vdate = @date
         VSuccess = @SelectTreeItem("Search Update Menu!Search (F7)")
         FormFieldValue("Time Clock", "TimeClockName", 0, "..EXAMPLE..")
         FormFieldValue("Time Clock", "TimeClockDate", 0, Vdate)
         FormFieldValue("Time Clock", "TimeClocktimeout", 0, "=")            
         VSuccess = @SelectTreeItem("Search Menu!Search Commands!Retrieve New Results (F10)")
         @exit
 

The problem I have with the example above is if the user hits the button and the result set does not find any records, it remains in the search screen. The user can then change the search spec to find any other worker or date and search for it. I do not want this to happen. I would like the program to go back to the main menu if the search result does not find any new records. I tried to add the following:

If @Mode() = 2 Then
     SetDefaultTab("Add Data Menu")
               vMenu1 = @SelectTreeItem("Clock!Forms!Add Data!Clock!Menu")

However, this would go back to the main menu every time.


My second question, is there anyway to prevent the operator from hitting “F7” to initiate a search if they are already in update mode?

Any advice or help would be greatly appreciated.

Thanks,

Kevin
E & S Gage

Ben:

Thank you for the suggestion. However, I just tried it and it did the same thing. It immediately went back to the main menu before the operator could clock out. With or without a found search spec. It pretty much did what my example did. Also, if you know of a way in security to disallow search mode that would be a great help.

Thanks.

2.0.6

Hammer:

OK, thanks for the advice, I will do that, and I really appreciate your time to help. So I guess what you are saying is there is no way in security or in a programming statement to prevent a user from being in the Update mode and hitting F7 on the keyboard to enter the search mode. Even if I do as you suggest, it seems to me once they are working in the update mode of their current record, they could still press "F7" and enter the search mode. That is what I am trying to avoid. Perhaps I am not getting my question across properly. I want all searches to be controlled by the command buttons and not by them manipulating it with "F7."


Thanks again!!

Hammer:

Thank you very much again. I will play around with XResultSet and see what I come up with.