View Single Post
  #1   Report Post  
Posted to microsoft.public.excel.programming
Chechu Chechu is offline
external usenet poster
 
Posts: 23
Default EOMONTH compatibility issue (workaround?)

On Jun 5, 11:26*am, joel wrote:
In general using simple worksheet functions on a worksheet is more
efficient that calling a UDF VBA function. *There is an overhead
associated with calling a VBA function and VBA code is less eficient
that worksheet function in memory and speed.

Some worksheet functions use a lot of memory resources and slow down a
worksheet such as SUMPRTODUCT and using array functions (ones where you
put a curly bracket {} around the function).

VBA Macros macros can be used to speed up a workbook since worksheet
functions get automaticaly updated every time you make new entries on a
worksheet while VBA code can be run be run manually. *There are lots of
exceptions to these generalizations so use them only as guidelines.

--
joel
------------------------------------------------------------------------
joel's Profile:http://www.thecodecage.com/forumz/member.php?u=229
View this thread:http://www.thecodecage.com/forumz/sh...d.php?t=207360

http://www.thecodecage.com/forumz


Thanks for your comments Joel. So based on it, it seems that option 2
(replace EOMONTH with formula =DATE(YEAR(start_date),MONTH(start_date)
+months
+1,0) ) should be more efficient??
Thank you,
Cecilia