"autofill" a sequential date field

[Guest]

I'm one of about a thousand+1 working on a timesheet. So far so good. All I
need is for my 7 date fields to automatically fill with sequential dates
derived from my "week beginning" field. How might I do this?

P.S. I know nothing about script, VBA, or code so be gentle. Oh, I'm using
Access 2002.

 

[Joseph Meehan]

I'm one of about a thousand+1 working on a timesheet. So far so good.
All I need is for my 7 date fields to automatically fill with
sequential dates derived from my "week beginning" field. How might I
do this?

P.S. I know nothing about script, VBA, or code so be gentle. Oh, I'm
using Access 2002.

How about a little more information What determines a new record. A
new week, a different employee... Will you need to fill in this data each
week for all records. How many records? Will the old data be maintained?
Is there a reason you have seven fields rather than a related table with
seven records?

 

[Guest]

new record = beginning of week (each record is counted by Timesheet # as you
will see)
fill in this data each week for all records - yes

Is there a reason you have seven fields rather than a related table with
seven records? I have one table that includes:

Timesheet # (autonumber and key)
employee
week beginning
Date (1-7)
Hours (1-7)
Travel, Straight, OT,DT (1-7)
Job # (1-7)
Service Ticket # (1-7)
Per Diem (1-7)
Job Name (1-7)
Odometer Start (1-7)
Odometer End (1-7)
Job Description (1-7)

(1-7)= each day of the week

This will be accessed by each employee via the web on our company server on
each Friday (or so) to have a report on Tue. of the following week.

I'm not sure I'll have any problems with this, but, in my .html page I have
all labels across the top of the page (Employee, Date. etc.) I have taken
each repetative label and renamed them all the same (They were Date1:,
Date2:, etc. - changed the InnerText) and transposed them all on top one
another and placed each consecutive text box in a column below the "one"
label for each day of the week. So it looks something like this:
__________ _____________
Employee |_________| Week Beginning |____________|

Date Hours Travel <-----all in layers
___________ _________ _________
|__________| |________| |________| <---- represents "Travel1:"
___________ _________ _________
|__________| |________| |________| <---- represents "Travel2:"
___________ _________ _________
|__________| |________| |________| <---- represents "Travel3:", etc.
___________ _________ _________
|__________| |________| |________|
___________ _________ _________
|__________| |________| |________|
___________ _________ _________
|__________| |________| |________|
___________ _________ _________
|__________| |________| |________|

Lost, ok.

I want to put in the "week beginning" date and have all of my "Date" fileds
fill in automatically...or am I asking too much?

 

[Joseph Meehan]

new record = beginning of week (each record is counted by Timesheet #
as you will see)
fill in this data each week for all records - yes

Is there a reason you have seven fields rather than a related table
with seven records? I have one table that includes:

Timesheet # (autonumber and key)
employee
week beginning
Date (1-7)
Hours (1-7)
Travel, Straight, OT,DT (1-7)
Job # (1-7)
Service Ticket # (1-7)
Per Diem (1-7)
Job Name (1-7)
Odometer Start (1-7)
Odometer End (1-7)
Job Description (1-7)

(1-7)= each day of the week

This will be accessed by each employee via the web on our company
server on each Friday (or so) to have a report on Tue. of the
following week.

Let's think about this much first.

I am thinking you may need three tables.

Employee with demographics information and an identifying number. You
may already have this in another database and assuming it meets your needs
you may want to link to that table in that database to avoid out of sync
issues.

Next I would have a time sheet table including week beginning and an ID
number.

Third table would be day's travel activity and have the following
fields

Linking field to the time sheet table (UD number)
Date
Hours
Travel, Straight, OT,DT
Job #
Service Ticket #
Per Diem
Job Name
Odometer Start
Odometer End
Job Description

The Day's travel activity table would be a subform in datasheet few
showing one weeks (7) records.

I am suggesting getting this part of the project normalized first
because it should make the rest easier and more business like.

 

[mmellring]

Let's think about this much first.

I am thinking you may need three tables.

Employee with demographics information and an identifying number. You
may already have this in another database and assuming it meets your needs
you may want to link to that table in that database to avoid out of sync
issues.

Next I would have a time sheet table including week beginning and an ID
number.

Third table would be day's travel activity and have the following
fields

Linking field to the time sheet table (UD number)
Date
Hours
Travel, Straight, OT,DT
Job #
Service Ticket #
Per Diem
Job Name
Odometer Start
Odometer End
Job Description

The Day's travel activity table would be a subform in datasheet few
showing one weeks (7) records.

I am suggesting getting this part of the project normalized first
because it should make the rest easier and more business like.