Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM General » View Thread |
Messages 1 to 2 of 2 total |
Why a table should trigger a key down event? |
Thu, Jul 28 2011 9:07 AM | Permanent Link |
marcioehrlich | A particular table in one of my forms is triggering a formkeydown event every time it opens or closes.
I've already tried to trap each and every table event that I've set (afterscroll, beforepost a.s.o.) but the flow never goes there between the opening/closing and the formkeydown. But after a Table1.Open or a Table1.Close, the debugger shows me I'm always trown to the formkeydown event. Inside the formkeydown I've detected the key is #37 (left arrow), which makes less sense to me. Why may that be happening and how can I avoid it? Thanks, Marcio |
Thu, Jul 28 2011 10:17 AM | Permanent Link |
Roy Lambert NLH Associates Team Elevate | marcioehrlich
With the information given its pretty near impossible to tell what's going on. AFAIK opening / closing a table will not send a key down message so I'd suspect your code. Looking at just the table's events is a bad place to start since opening / closing will have an impact on any data aware control linked to the table (ie the OnStateChange for a TDataSource for definite). You need to look at all the events of all controls that might be affected. Roy Lambert [Team Elevate] |
This web page was last updated on Saturday, April 27, 2024 at 08:52 PM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |