>>Hi Cindy,
>>
>>Given that I deal a lot with fiscal months and years, I should've caught this possibility. In these situations, what I do is have a table containing the month name, and the starting and stopping dates for the period. I then use a query utilizing BETWEEN to retrieve the applicable information. Since I still need the date field, this allows me to utilize that, rather than having to populate an additional field.
>
>George,
>
>Some of my data comes in with the FiscalPeriod assigned already, so I'm more likely to use that than derive it from a date. The actual date is only of secondary importance for me.

In my case, the period can be as short as one day and as many as the user desires. So for my situation, I think that this gives the user the easiest interface to deal with. Basically, there's an option group with the buttons named, "Daily", "Weekly", "Monthly", "Quarterly", and "User Defined". If either "Monthly" or "Quarterly" is selected a combo box (as a drop down list) is populated appropriately. Then the user only has to select either the month or quarter desired from the list. This then sets the values of the beginning and ending dates text boxes acordingly, depending on the user's selection.

>In any case, this will give Moises some ideas for his design.

Yep, and that's the most important thing.