From: מיכאל (מיקי) אבידן on 4 Apr 2010 07:22 I have no intention to challenge Billns's, or any others assumption all I had in mine is the lack of possibility to run calculations with your solution. I also prefer the ALL YEARS Workbook_Change solution suggested by [Toms wasn't there when I first responsed]. I can assure you that I face a lot of questions where the OP writes 2009 and after getting solutions) that are directed to meet only the year 2009 he returns to ask "...and what if I want it to be applied to another year". This is what I, usually, try [maybe not always successfully] to avoid] and therefor try to present as general solution that I can think of except for cases where the OP makes it very clear that he is looking for a specific solution. Hope I made myself clear. Micky "Joe User" wrote: > "מיכאל (מיקי) אבידן" <micky-a*at*tapuz.co.il> wrote: > > This might solve the typing and "appearance" but produce woeful results, > > if he needs to run any calculations on those "dates" > > My comments make the same assumption that Billns makes, namely: "if the > dates are __all__ last year". Since neither 2009 nor 2010 is a leap year, I > believe, as Billns's does, that date calculations will have the same result > regardless of which year is actually used. > > If your point is to challenge Billns's assumption, that's fine. But he did > say "if". It is up to JCarlos (and others) to read the comments carefully. > > That said, I would prefer the Workbook_Change solution suggested by Don and > Tom. It is the more general solution for __all__ years. > > > ----- original message ----- > > "מיכאל (מיקי) אבידן" <micky-a*at*tapuz.co.il> wrote in message > news:CA88880A-9769-4552-83D5-D80118BB8BB8(a)microsoft.com... > > This might solve the typing and "appearance" but produce woeful results, > > if > > he needs to run any calculations on those "dates" - and he didn't > > emphasize > > that he do not... > > Micky > > > > > > "Joe User" wrote: > > > >> "Billns" <billns(a)nsverizon.net> wrote: > >> > If the dates are all last year, why do you even need to display the > >> > year or care which one it really is? Format the column as mm/dd. > >> > >> Or if JCarlos would like the date to __appear__ as 2009, enter dates in > >> the > >> form mm/dd, but use the Custom format mm/dd/"09" or something like that. > >> > >> > >> ----- original message ----- > >> > >> "Billns" <billns(a)nsverizon.net> wrote in message > >> news:%237u1fH10KHA.220(a)TK2MSFTNGP06.phx.gbl... > >> > On 4/3/2010 9:39 AM, JCarlosJr wrote: > >> >> Hi gang, > >> >> > >> >> Its tax time and I'm trying to enter my expenses ito EXCEL for last > >> >> year > >> >> (don't even remind me I should do this as the year progresses). > >> >> > >> >> Anyway, for speed of entry I would like to enter just mm/dd. Excel > >> >> will > >> >> complete the year for me as 2010. > >> >> > >> >> I could change the system date, but this has bad reprocussions, > >> >> especaill > >> >> when multi-tasking. > >> >> > >> >> I could create a column which subtracts 365 from my entry column and > >> >> then > >> >> paste values from my "dummy" column into my entry column. > >> >> > >> >> BUT, does anyone have a better suggestion to force dates entered on a > >> >> specific book, sheet, or even colum to s different default year than > >> >> the > >> >> system date year? > >> >> > >> > > >> > If the dates are all last year, why do you even need to display the > >> > year > >> > or care which one it really is? Format the column as mm/dd. > >> > > >> > Bill > >> > >> . > >> > > . >
First
|
Prev
|
Pages: 1 2 3 Prev: WHY IS FREEZE PAINS GREYED OUT Next: alignment in a validation list |