Jim Dettman
jimdettman at earthlink.net
Wed Jul 14 11:10:49 CDT 2004
Susan, I've always heard that it's in the 10-15% range, which the few times that I've bothered to check, seems to be about right. You do notice the difference. Jim Dettman (315) 699-3443 jimdettman at earthlink.net -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Susan Harkins Sent: Wednesday, July 14, 2004 11:18 AM To: 'Access Developers discussion and problem solving' Subject: RE: [AccessD] more on early versus late binding My understanding is it's each time you use it because VBA has to go get the particular info for the property, method, whatever. I'm also curious about the speed issue -- I think many times, the things we "learn" are holdovers from the old days when systems really were slow and memory really was an issue. I can't imagine the performance hit for even being noticeable. But then, you might actually see it -- I know I've got a list box that drives me nuts -- first time I use it every day, it takes a second or so to load -- so if this is happening every time... It might actually be important. Does anyone have in actual experience to share on the speed issue? Susan H. John: Another clarification, please: "...every time the function is called." Does this mean every time the "Set ojbX = " is executed or every time I reference the object while I've got the object open. I might set an object to a spread sheet or word doc once but refer to it thousands of times before I close it. And maybe I'm writing simple apps, but I've pretty much given up trying to optimize my code up front for speed and gone for clarity and maintainability instead. Because it doesn't seem to make any difference. I rarely have a client say something is running too slow. -- _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com