L
Larry R Harrison Jr
I have an Access 97 database designed for scheduling. It shows numbers of a
certain part ran for different weeks. The structure of the table is like
this:
*****************************************************************
autoid--autonumber (obvious)
machineid--number--holds "id" of machine ran (there's another machine table,
this links to it)
date1--date/time--the date this is done
shift1--number--1,2,3 (representing the shift)
partid--number--holds "id" of part ran with this machine (there's another
part table, this links to it)
qty--number--# of units ran
prior--number--the priority of this run
comment--text--allows comments
sample--yes/no--marks it as a sample
*****************************************************************
The form does not directly link to this table as a normal RECORDSOURCE. In
fact the form is unbound and the values are "filled in" with code. That way,
it looks like a Sunday-Saturday schedule. It does this by figuring out which
date is Sunday from today's date, which date is Saturday, finding entries
that match that criteria, and "filling in" the form. It uses a host of
DLOOKUP statements to do this. (If it doesn't find any matches, it prompts
the user and gives them the change to create these entries automatically;
SQL statements in Visual Basic are used obviously.) I could post the code,
but it's lengthy.
So here's the thing--now I need a printable report which shows much the same
thing. I'm guessing maybe some sort of crosstab query would be in
order--with the report based on this query. Am I right?
Tips? If it is a crosstab query, I may need help in that regard making it;
despite my SQL and Visual Basic abilities, crosstab queries are a hard one
for me.
LRH
certain part ran for different weeks. The structure of the table is like
this:
*****************************************************************
autoid--autonumber (obvious)
machineid--number--holds "id" of machine ran (there's another machine table,
this links to it)
date1--date/time--the date this is done
shift1--number--1,2,3 (representing the shift)
partid--number--holds "id" of part ran with this machine (there's another
part table, this links to it)
qty--number--# of units ran
prior--number--the priority of this run
comment--text--allows comments
sample--yes/no--marks it as a sample
*****************************************************************
The form does not directly link to this table as a normal RECORDSOURCE. In
fact the form is unbound and the values are "filled in" with code. That way,
it looks like a Sunday-Saturday schedule. It does this by figuring out which
date is Sunday from today's date, which date is Saturday, finding entries
that match that criteria, and "filling in" the form. It uses a host of
DLOOKUP statements to do this. (If it doesn't find any matches, it prompts
the user and gives them the change to create these entries automatically;
SQL statements in Visual Basic are used obviously.) I could post the code,
but it's lengthy.
So here's the thing--now I need a printable report which shows much the same
thing. I'm guessing maybe some sort of crosstab query would be in
order--with the report based on this query. Am I right?
Tips? If it is a crosstab query, I may need help in that regard making it;
despite my SQL and Visual Basic abilities, crosstab queries are a hard one
for me.
LRH