From: Fred on
Dennis,

It's good to question your structure, because that it the foundation for
everything else. But defining your structure well requires an understanding
of the real-world process that you want to database, and the mission(s) that
you want the database to accomplish. From your post, it looks like you have
put a lot of goo thought into that area. However, since you have not
informed us enough on real-world process that you want to database, and the
mission(s) that you want the database to accomplish, we can't really review
your structure for you.

So, if you want us to analyze it, you'll need to tell us the above. If you
prefer to analyze it yourself, you might start by making a list of the
prospective entities to database. You might start those of your listed
tables:


- Work Orders
- whatever entity that second table is
- Work Order Details
- Expense Reports
- Expense Report Details

And consider a few other possible entities:

Invoices
Customers
Employees


You'll have to decide whether or not invoices are an entity (which heavy
duty systems treat them as) or not (which is how all 100% of the Access
examples I've seen treat them)

Make sure all of the data in each table is of "one-to-one" type with it's
entity. If not, split it.

See if the entities in any two tables are in a pure one-to-one relationship
with each other. If so, combine them into one table.

Well, there a few thoughts. Good luck.



From: Dennis on
Allen,

Allen,

I agree with your comment. Since this was both a database and report issue,
I originally tried to post to both group using the usenet address, but I
screwed up somehow.

Once Jeanette answered my questions, I want to know how to create a total
for invoice with different sub-forms. That is why I posted the question in
the report group.

But I guess I should have waited a day or so before I posted to the other
group.
You point is well taken.

Thanks again.

Dennis

"Allen Browne" wrote:

> Dennis, as Jeannette says, you can do what you need with this structure.
>
> In another group where you posted the same question, I suggested another
> structure for you.
>
> One of the problems with posting the same question to multiple groups is
> that your responses get fragmented, i.e. it limits the way the responses
> flow for you.
>
> --
> Allen Browne - Microsoft MVP. Perth, Western Australia
> Tips for Access users - http://allenbrowne.com/tips.html
> Reply to group, rather than allenbrowne at mvps dot org.
>
>
> "Dennis" <Dennis(a)discussions.microsoft.com> wrote in message
> news:2B1E08A6-3385-45B6-95EA-AD40339A9C4B(a)microsoft.com...
> > Jeanette,
> >
> > Thanks.
> >
> > Is the database structure ok? I wasn't sure if I was having problems the
> > database structure or the report. When I finally wrote out my questions,
> > I
> > thought about the sub-report you suggested. But I was not sure if my
> > conceptualization issue is with my db structure of my vison of the
> > invoice.
> >
> > Thanks for you advice.
> >
> > Dennis.,
>
> .
>
From: Dennis on
Fred,

Thanks for the input. You are absolutely correct, I should have included a
description of the real world process. I will do that next time.

As Allen Browne stated, he answered the question in a post in the report
section. As stated in my first entry, I tried to post to two group (Database
and Report) because I felt this had issues for both group.

In case anyone else reads this, here is the link to the other question and
Allen's answer:


http://www.microsoft.com/communities/newsgroups/en-us/default.aspx?&lang=en&cr=US&guid=&sloc=en-us&dg=microsoft.public.access.reports&p=1&tid=7514f434-76de-4a4a-9b3f-fd173f45d14c



Dennis