Bill Benson
bensonforums at gmail.com
Wed Sep 24 21:51:43 CDT 2014
Not sure it is right to say 80 modules is excessive without knowing the application, in particular if, as was suggested elsewhere, some of these are class modules. Every worksheet can have a code module, some workbooks can have hundreds of worksheets - and sometimes there are ActiveX CommandButtons that have their click event within the sheet's code module. So that would be potentially hundreds of sheets. I also remember reading that code for incompatible versions of Excel can be placed into separate code modules and therefore one needs to worry about runtime compilation only in the modules whose procedures are called; presumably testing for version before deciding which proc to call. -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Mark Simms Sent: Wednesday, September 24, 2014 10:36 PM To: 'Access Developers discussion and problem solving' Subject: Re: [AccessD] DoCmd.OpenModule for Access - Something similar for Excel ? Sorry to disagree....80 modules ? That's excessive IMHO. My largest app has about a dozen. Also disagree about stability....Excel VBA much less stable than Access VBA. Excel under Citrix or a virtual Windows environment is darn outright unstable.....VBA crashes often. > > On the other side of the coin, I have built many Excel workbooks with > 80+ > modules that have been extensively used in the past without issue. -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com