John Colby
jwcolby at gmail.com
Fri Dec 13 14:22:37 CST 2013
License to vent my friend, license to vent! On 12/13/2013 3:20 PM, Tony Septav wrote: > Hey John > Come on old one, we have known for years (since 1998) if you go up and > search out ACCESS errors the list will totally dumbfound you. > > Tony Septav > Nanaimo, BC > Canada > > > > > -----Original Message----- > From: accessd-bounces at databaseadvisors.com > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of John Colby > Sent: December-13-13 2:12 PM > To: Access Developers discussion and problem solving > Subject: Re: [AccessD] I just gotta vent > > Shamil, > > Thanks for validating the bug. I am using Windows 7 and Access 2007. > > Which tells me that they haven't decided that bugs are an important > thing to work on, even in 2013. > > Yes, on abandoning. > > OTOH I have a job (for IBM no less) maintaining Access databases. I am > not allowed to "abandon" them. ;) > > On 12/13/2013 3:05 PM, Salakhetdinov Shamil wrote: >> Hi John -- >> >> I didn't know about this bug, sorry. >> >> Just out of curiosity I have: >> >> - created a bound test form, >> - set its recordsource to filter out all records (ID = -1); >> - set AllowAdditions = False; >> - created a search textbox named txtSearch in the form's header; >> - created a search value copy textbox named txtCopy in the form's header; >> - set OnChange event procedure to >> >> Private Sub txtSearch_Change() >> txtCopy.Value = txtSearch.Text >> End Sub >> >> - opened test form in Normal view and typed a char in txtCopy textbox - > *bang* >> 2185 - You can't reference a property or method for a control unless the > control has the focus. >> In my test I have used Win8 and MS Access 2013. >> >> There seems to be no effective workaround of this bug. >> >> This is a typical bug case one of many others, which forced me to abandon > MS Access/VBA development. >> Thank you. >> >> -- Shamil >>