[AccessD] KeyDown Problem

Charlotte Foust cfoust at infostatsystems.com
Fri Mar 17 12:15:20 CST 2006


The nearest I've been able to figure is that some of the recent updates
have affected compiler.  It is completely maddening, but not nearly as
much as the similar behavior in VS 2005! :oS


Charlotte

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Rocky Smolin
- Beach Access Software
Sent: Friday, March 17, 2006 9:59 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] KeyDown Problem

It just happened again. I'm beginning to think there's a setting or
something not set correctly.

I copied an existing subform, made some mods to the new one (since it
was similar to the old one) and dropped it onto a tab form.  A double
click event in a text box on the tab form but NOT in the sub form
refused to fire.  Went to code.  Compiled.  Clean!

Eventually I figured out that I had forgotten to delete all the code
behind sub form when I copied the old sub form to the new one.  The new
one was referencing controls on the old sub form which weren't on the
new one.  But no compile error.

Deleted all the code behind the new sub form and everything worked.  But
the compile was clean.  And yes I do have OPTION EXPLICIT in every page
of code I write.

Any ideas what's causing this?

Regards,

Rocky


Charlotte Foust wrote:
> Well, it IS Friday, so we can all go nuts together!  LOL
>
>
> Charlotte
>
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Rocky 
> Smolin
> - Beach Access Software
> Sent: Friday, March 17, 2006 9:14 AM
> To: Access Developers discussion and problem solving
> Subject: Re: [AccessD] KeyDown Problem
>
> Once again, I find that I am not losing my mind. (Or have company
> anyway)
>
> Rocky
>
>
> Charlotte Foust wrote:
>   
>> I have, and it drove me crazy!  When strange things start occurring, 
>> I
>>     
>
>   
>> immediately do a compile.  The thing that's making me nuts now is, 
>> after installing Office 2003 but keeping Access 2002, this has become

>> even more frequent.  Error messages will pop up that occur deep down 
>> in the stack but they present an obtuse message that is less than 
>> useless and I have to step through layers of code to find the line
>>     
> that blows up.
>   
>> Charlotte Foust
>>
>> -----Original Message-----
>> From: accessd-bounces at databaseadvisors.com
>> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Rocky 
>> Smolin
>> - Beach Access Software
>> Sent: Friday, March 17, 2006 6:16 AM
>> To: Stuart McLachlan; Access Developers discussion and problem 
>> solving
>> Subject: Re: [AccessD] KeyDown Problem
>>
>> Stuart:
>>
>> Thanks.  That would be the global solution. 
>>
>> Had another weird problem occur - one of my events stopped working 
>> altogether.  It was a click event.  Other events continued to work, 
>> this one just wouldn't.  Eventually I traced it down to a compile 
>> error in an unrelated module - it was in another form's code! Once I 
>> had a clean compile, the click event worked.  Any compile error and 
>> this event stopped.  Although other events continued to work
>>     
> correctly.
>   
>> Ever seen this behavior before?
>>
>> Regards,
>>
>> Rocky
>>
>>
>> Stuart McLachlan wrote:
>>   
>>     
>>> On 16 Mar 2006 at 5:58, Rocky Smolin - Beach Access Software wrote:
>>>
>>>   
>>>     
>>>       
>>>> Stuart:
>>>>
>>>> Thanks for having a look at this.  (You might have to relink the 
>>>> back
>>>>       
>>>>         
>>   
>>     
>>>> end tables.)
>>>>
>>>> Login as Curly - password curly. 
>>>>
>>>> The tabbed form and KeyDown routine are in the Orders form off the 
>>>> Main Menu.  The tabbed form IS full of sub-forms.  Someone 
>>>> suggested
>>>>         
>
>   
>>>> that might be causing problems.
>>>>
>>>>     
>>>>       
>>>>         
>>> Yes, that's it.  Once you tab to another page, the subform gets the 
>>> focus and that subform doesn't have KeyPreview on.  You will need to

>>> set keypreview on for all the subforms. Then call a generic 
>>> procedure
>>>     
>>>       
>> in the keydown to shift focus back to where you want it.
>>   
>>     
>>>  
>>>   
>>>     
>>>       
>> --
>> Rocky Smolin
>> Beach Access Software
>> 858-259-4334
>> www.e-z-mrp.com
>>
>> --
>> AccessD mailing list
>> AccessD at databaseadvisors.com
>> http://databaseadvisors.com/mailman/listinfo/accessd
>> Website: http://www.databaseadvisors.com
>>   
>>     
>
> --
> Rocky Smolin
> Beach Access Software
> 858-259-4334
> www.e-z-mrp.com
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>   

--
Rocky Smolin
Beach Access Software
858-259-4334
www.e-z-mrp.com

--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com



More information about the AccessD mailing list