Dates: Just MM-YYYY?

[(PeteCresswell)]

I've got an app whose purpose in life is to do technical analysis of bond fund
returns.

Each return has a "Date", but the "Date" is really just a month/year.

i.e. The return for January of 2005 or the return for April of 1996.

Right now, to placate VBA and have use of the various date functions I'm storing
all the return dates with Day=01 - explicitly typed in by the user or assigned
by code that processes Copy/Pastes from Excel spreadsheets.

A few days ago, I stumbled onto the realization that if I typed "8/2005" into a
query's date prompt, whatever was between me and the query happily accepted it
as 08/01/2005. In fact, in the Immediate window I find:

?DateValue(#8/2005#)
08/01/2005

This got me thinking that I should shield the users from having to type that
"/01/" in every time they enter a return/date. Right now, I'm edit-checking
for the "01", but it seems to me like they should never even have to see the day
part of a return date.

I see the obvious like .InputMask and .Format, but don't know the full
implications of doing something like this - and I don't want to foul something
up that doesn't surface until months later...

Anybody actually been here?
--
PeteCresswell

[Dean]

I avoid this mess by using a monthend date. So in your case it would
be 08/31/05. The formula to calculate these things is:
DateSerial(Year(Date()),Month(Date())+1,1)-1

I have never tried it your way, but I'll look into it.