Advice on a calendar and data

I am working on a project that looks like a calendar for scheduling where
each day is a frame with a nurse's name a time in and time out and other
info on it. The Calendar displays upto 31 days or shifts at a time on the
same form.
Right now the database record has fields for one day/shift of info, but I
need to show 31 different records at once. The data source use on a textbox
will just display 31 views of the same one record. How can I get each one
to refer to a different record. Now I am trying to decide the best way to
do this:
a) Should I make the record in the database have enough fields for a week
of shifts and then have 4-5 recordsets one for each week.
b) Should I make a day control that can show different records and if so
How can I do that.
c) I could make the record have fields for 31 days but that would be like
8x31 fields.
d) Anything anyone else can think of. Or is there a way to have a data source
show a the same field on a different record?

"Ed Marquez" <edneeis@netscape.net> wrote:
>
>I am working on a project that looks like a calendar for scheduling where
>each day is a frame with a nurse's name a time in and time out and other
>info on it. The Calendar displays upto 31 days or shifts at a time on the
>same form.
>Right now the database record has fields for one day/shift of info, but
I
>need to show 31 different records at once. The data source use on a textbox
>will just display 31 views of the same one record. How can I get each one
>to refer to a different record. Now I am trying to decide the best way to
>do this:
>a) Should I make the record in the database have enough fields for a week
>of shifts and then have 4-5 recordsets one for each week.
>b) Should I make a day control that can show different records and if so
>How can I do that.
>c) I could make the record have fields for 31 days but that would be like
>8x31 fields.
>d) Anything anyone else can think of. Or is there a way to have a data source
>show a the same field on a different record?


Hi Ed,
Why not use a crosstab query to pull the data you want into a recordset and
then use that to populate the calendar? Would this do what you want?

Hope this helps,
Mark.

Well I can get the info I need the problem is in the inputing of new data
because there would be 31 textboxs that need to show 31 different records
at the sametime and so that the user can change, add, update whatever each
record individually, but keep in mind all 31 record need to accessable at
all times.

"Mark" <mmannic@gte.net> wrote:
>
>"Ed Marquez" <edneeis@netscape.net> wrote:
>>
>>I am working on a project that looks like a calendar for scheduling where
>>each day is a frame with a nurse's name a time in and time out and other
>>info on it. The Calendar displays upto 31 days or shifts at a time on the
>>same form.
>>Right now the database record has fields for one day/shift of info, but
>I
>>need to show 31 different records at once. The data source use on a textbox
>>will just display 31 views of the same one record. How can I get each one
>>to refer to a different record. Now I am trying to decide the best way
to
>>do this:
>>a) Should I make the record in the database have enough fields for a week
>>of shifts and then have 4-5 recordsets one for each week.
>>b) Should I make a day control that can show different records and if so
>>How can I do that.
>>c) I could make the record have fields for 31 days but that would be like
>>8x31 fields.
>>d) Anything anyone else can think of. Or is there a way to have a data
source
>>show a the same field on a different record?
>
>
>Hi Ed,
>Why not use a crosstab query to pull the data you want into a recordset
and
>then use that to populate the calendar? Would this do what you want?
>
>Hope this helps,
>Mark.
>

"Ed" <edneeis@netscape.net> wrote:
>
>Well I can get the info I need the problem is in the inputing of new data
>because there would be 31 textboxs that need to show 31 different records
>at the sametime and so that the user can change, add, update whatever each
>record individually, but keep in mind all 31 record need to accessable at
>all times.
>
>"Mark" <mmannic@gte.net> wrote:

I did something similar to this using the MSFlexGrid. Because a crosstab
is not an updatable query, I displayed the data in the grid, then when the
user right-clicked on a cell, I popped up an edit window for that particular
record. Then it is a simple matter to execute an update statement for that
record, and refresh the crosstab query.
You can keep track of which date relates to each cell in the grid by using
an array as you load it or by some other means.

I hope this will at least give you some ideas,
-Mark.