ObVBASucks

Post #155,833 by inthane-chan 5/18/04 9:22:54 PM Reply	ObVBASucks So, in Visual Basic, if you want to grab an event that a control triggers, you name the event <control>_<event>. So, if your control was called cmdOK, and you wanted to catcht the "OnClick" event, you do the following: Sub cmdOK_OnClick()\n ' Stuff here\nEnd Sub Guess what? Under VBA in Access, you need to take one more step - select the control, switch to the Properties window, select "Events", find the appropriate event (not always with the same name as the event is referred to, either) and change it to some other value that escapes me right now. Spent 3/4 a fucking hour tracking down that fucking bug. Also explains some other squirrely behavior I've seen elsewhere in my app. Tired of lying in the sunshine staying home to watch the rain. You are young and life is long and there is time to kill today. And then one day you find ten years have got behind you. No one told you when to run, you missed the starting gun.
Post #155,840 by ben_tilly 5/18/04 9:52:48 PM Reply	A taste of things to come... To deny the indirect purchaser, who in this case is the ultimate purchaser, the right to seek relief from unlawful conduct, would essentially remove the word consumer from the Consumer Protection Act - [link\|http://www.techworld.com/opsys/news/index.cfm?NewsID=1246&Page=1&pagePos=20\|Nebraska Supreme Court]
Post #155,842 by FuManChu 5/18/04 10:09:30 PM Reply	Everything's easier with the mouse, right? ;)
Post #155,860 by CRConrad 5/19/04 2:48:58 AM Reply	OTOH, are you sure you even have to name it like that? I mean, if the way to associate an event handler with an event is to select the handler in the event's drop-down property selector, then it shouldn't matter what the event handler is called... And in fact, my vague recollection from VB (the "real" non-A VB, ages ago; VB 4 or possibly 5, IIRC) is that the name didn't, in fact, matter. Are you really sure that the "magical naming" works in any other version, without explicitly associating the handler with the event by selecting it in the property inspector (or whatever MS calls that window)? 'Coz I actually doubt that even MS could make things that backwards... I rather suspect that the "magical name", that you seem to think should be sufficient to associate the handler with the event, is just the default name that the IDE comes up with if you let it create the (skeleton of an) event handler for you, by double-clicking on the event-handler property in the property inspector. In short, I really don't think it's a "bug"; I think it's that you haven't fully grokked the functioning of event-based programming IDEs. HTH! [link\|mailto:MyUserId@MyISP.CountryCode\|Christian R. Conrad] (I live in Finland, and my e-mail in-box is at the Saunalahti company.) Your lies are of Microsoftian Scale and boring to boot. Your 'depression' may be the closest you ever come to recognizing truth: you have no 'inferiority complex', you are inferior - and something inside you recognizes this. - [link\|http://z.iwethey.org/forums/render/content/show?contentid=71575\|Ashton Brown]
Post #155,863 by altmann 5/19/04 3:39:51 AM Reply	Yes Access is a little weird in that area. The event procedure name has to match the pattern object_event (though you leave off the "On" for the event). The magic phrase that goes in the event property is [Event Procedure] which tells Access to look for the corresponding procedure with the above formatted name. You can also put the name of a macro or an expression starting with "=" (the later could be a way to call an alternate procedure) in the field. So it isn't a bug, it's just different. -- Chris Altmann
Post #155,864 by CRConrad 5/19/04 3:45:04 AM Reply	Silly me... ...'coz I actually "doubt[ed] that even MS could make things that* backwards"! I have no real idea why I did that. I'll try not to do it again. [link\|mailto:MyUserId@MyISP.CountryCode\|Christian R. Conrad]* (I live in Finland, and my e-mail in-box is at the Saunalahti company.) Your lies are of Microsoftian Scale and boring to boot. Your 'depression' may be the closest you ever come to recognizing truth: you have no 'inferiority complex', you are inferior - and something inside you recognizes this. - [link\|http://z.iwethey.org/forums/render/content/show?contentid=71575\|Ashton Brown]
Post #155,872 by jbrabeck 5/19/04 7:35:41 AM Reply	Just wait until he tries to clone an object. It ain't an object! Code doesn't come with the object. (If it does, could someone tell me how. I hate first copying the GUI object, then going into VBA and copying the associated code, then renaming the object part of the code to make it work)
Post #155,962 by altmann 5/19/04 4:45:47 PM Reply	VB.Net, C# and Delphi are the same way (new thread) Created as new thread #155961 titled [link\|/forums/render/content/show?contentid=155961\|VB.Net, C# and Delphi are the same way] -- Chris Altmann
Post #155,886 by mmoffitt 5/19/04 10:10:32 AM Reply	By the way... You're probably too smart to do this anyway, but I thought I'd warn you just in case this is the first time you've used Access as a dev tool. Save yourself a ton of grief later and do not use bound forms. In my consluting days I had to "fix" a rather largish Access application that used bound forms. It was hideous... bcnu, Mikem If you can read this, you are not the President.
Post #155,888 by jbrabeck 5/19/04 10:23:19 AM Reply	What's a "bound form"? I've been forced to use Access here and have learned via "trial and error".
Post #156,133 by mmoffitt 5/20/04 6:15:43 PM Reply	Controls bound to columns in the table/view. You don't have to write any code to update the Text properties, write to the db, etc. Requires access to base tables (a taboo in my book - but let's not go through that again) or at least updateable views. Others may differ, but w/Access if you use bound controls you have virtually no control over when your data gets updated. Also, performance really takes a hit, there are literally tons of reasons why "bound forms" (or "Data bound forms" is what I think MSFT calls them) are a very bad idea. bcnu, Mikem If you can read this, you are not the President.
Post #155,897 by inthane-chan 5/19/04 10:47:34 AM Reply	Yeah, I figured that out very quickly. Weird bugs cropping up in one form (I tend to be perfectionist, complete one form before going on to the next one) quickly made me decide to drop that "feature" entirely. Tired of lying in the sunshine staying home to watch the rain. You are young and life is long and there is time to kill today. And then one day you find ten years have got behind you. No one told you when to run, you missed the starting gun.

Welcome to IWETHEY!