text box event in a DAP

[kcddoorman]

This is done in an Access 2003 ADO data access page.

I've got a text box (txtSearch) and I've got a command button (cmdSearch).

The cmdSearch has this onclick event:

<SCRIPT language=vbscript event=onclick for=cmdSearch>
<!--
Dim rs
Set rs = MSODSC.DataPages(0).Recordset.Clone
On error resume next
 
rs.find "[WO NUMBER]=" & (txtSearch.value)
 
If (err.number <> 0) Then
    Msgbox "Error: " & err.number & " " & err.description,,"Invalid Search"
    Exit Sub
End If
cmdWOSearch.focus
 
If (rs.bof) or (rs.eof) Then
    Msgbox "Error Work Order not found.",,"Search Done"
    Exit Sub
End If
MSODSC.DataPages(0).Recordset.Bookmark = rs.Bookmark
cmdWOSearch.focus
-->
</SCRIPT>

When a user enters text into txtSearch and hits enter I would like to call the cmdSearch onclick event. As of now, all the enter key does inside the txtSearch box is create a new line.
Really this is three questions.
How to catch the enter key when it is pressed in the txtSearch box.
How to call an event from another event.
Are data access pages good to use?

[kcddoorman]

So I figured out question number two on my own. You can interact with other elements in the page like so. cmdSearch.focus or cmdSearch.click or cmdSearch.dblclick, pretty cool.

I'm not sure why this won't work. It may have something to do with ascii code in VBscript?
So I try this.

<SCRIPT language=vbscript event=onkeypress for=txtSearch>
<!--
dim KeyAscii
KeyAscii = Asc(UCase(Chr(KeyAscii)))
If KeyAscii = VbKeyEnter then
cmdSearch.click
End if
-->
</SCRIPT>

So for every key I press while txtSearch has focus this event will run. The problem is that this will catch everything. It won't weed out the return/newline/013/enter key that is pressed.
I thought maybe the page didn't like the VbKeyEnter criteria so I tried this

<SCRIPT language=vbscript event=onkeypress for=txtSearch>
<!--
dim KeyAscii
KeyAscii = Asc(UCase(Chr(KeyAscii)))
If KeyAscii = Asc(013) then ' I also tried chr(13) and chr(13) & chr(10)
cmdSearch.click
End if
-->
</SCRIPT>

This doesn't catch anything at all. The only thing I'm catching is a cold. Curse you fall season.

I'm not clear on how the event: onkeypress works I guess. I declare KeyAscii and use it to test for the chr(13) but how does the keypressed by the user get to be equal to KeyAscii? onkeypress is simply an event does it pass anything to the code? From what I'm reading about this Access may be eating my enter keypress.

[kcddoorman]

It has to be eating it. This code should work.

<SCRIPT language=vbscript event=onchange for=txtSearch>
<!--
dim searchstr
searchstr = txtSearch.onkeypress
Dim enter
enter = chr(13)
If searchstr = enter then
msgbox (enter) & "there it is",,"OK"
cmdSearch.click
Exit Sub
End If
-->
</SCRIPT>

I've read up about this problem in forms when the command button's property .default is set to true. How can I change this in a vbscript with MSODSC.

Thanks and I appreciate any light you may shed,
James

[ADezii]

This is done in an Access 2003 ADO data access page.

I've got a text box (txtSearch) and I've got a command button (cmdSearch).

The cmdSearch has this onclick event:

<SCRIPT language=vbscript event=onclick for=cmdSearch>
<!--
Dim rs
Set rs = MSODSC.DataPages(0).Recordset.Clone
On error resume next
 
rs.find "[WO NUMBER]=" & (txtSearch.value)
 
If (err.number <> 0) Then
    Msgbox "Error: " & err.number & " " & err.description,,"Invalid Search"
    Exit Sub
End If
cmdWOSearch.focus
 
If (rs.bof) or (rs.eof) Then
    Msgbox "Error Work Order not found.",,"Search Done"
    Exit Sub
End If
MSODSC.DataPages(0).Recordset.Bookmark = rs.Bookmark
cmdWOSearch.focus
-->
</SCRIPT>

When a user enters text into txtSearch and hits enter I would like to call the cmdSearch onclick event. As of now, all the enter key does inside the txtSearch box is create a new line.
Really this is three questions.
How to catch the enter key when it is pressed in the txtSearch box.
How to call an event from another event.
Are data access pages good to use?

1. The ENTER Key is probably not being recognized in the KeyPress() Event because you have the Move after enter Option set to Next Field (Tools ==> Options ==> Move after enter ==> Next Field).
2. All is not lost since you can trap the ENTER Key in the KeyDown() Event of [txtSearch], via the return value in the KeyCode Argument, then execute the Click() Event of cmdSearch as such:
   
   

   Private Sub txtSearch_KeyDown(KeyCode As Integer, Shift As Integer)
     Const conEnterKey = 13
    
     If KeyCode = conEnterKey Then
       Call cmdSearch_Click
     End If
   End Sub

[kcddoorman]

That would work great if it were in a form but this is a data access page.
Microsoft Says:
"VBScript is designed to be a small and lightweight interpreted language. It is also designed to be safe, so it does not include direct access to the underlying operating system. VBScript syntax and usage is similar to VBA, except that the following features and keywords are omitted:

Language elements such as: #Const, #If...Then...Else, CVar, CVDate, Date, Declare (for declaring DLLs), Debug.Print, DoEvents, End, Erl, Error, GoSub...Return, GoTo, Like, LinkExecute, LinkPoke, LinkRequest, LinkSend, LSet, Mid, On Error GoTo, On...GoSub, On...GoTo, Optional, Option Base, Option Compare, Option Private Module, ParamArray, Resume, Resume Next, RSet, Static, Stop, Str, StrConv, Time, Type...End Type, TypeOf, and Val"

I wonder if I could create a function that effects the page globally. The default event for pressing the enter key while a textbox has focus is to create a new line. This is being caught by something else. I just need to turn "it" off. What ever "it" is. It is so easy to do in a form with the on enter event, but alas there is no such animal in the DAP world of VBScript.

[kcddoorman]

Here is how you do it.
1. Open the Microsoft Script Editor
2. Select your textbox from the objects drop down list.
3. Select the onkeypress event from the events drop down list.
4. Insert this code between the <script>...</script>

if window.event.keyCode = 13 then
YOURBUTTONHERE.click()
end if
 

13 is the ascii number for the enter button you can use any button you want here.
So simple.

I also found another line of code that throws away the enter button so people are not entering the wrong(return carriage) data into the database.

<SCRIPT>
 
function kH(e) {
var pK = document.all? window.event.keyCode:e.which;
return pK != 13;
}
document.onkeypress = kH;
if (document.layers) document.captureEvents(Event.KEYPRESS);
 
</SCRIPT>

I appreciate your input on this topic. I hope I'm not getting a bad rap on here. I seem to post to my own questions more than anything. I should just keep a journal or something, but this way I get to share information for anyone who actually searches for their problem before asking the question.
Thanks for being my idea-bouncing-off-wall. thescripts FTW!