This is a continuation of a thread I started in the Queries forum. I had built my tables and my first few forms, but once I tried my first query, nothing worked. That thread is here: http://www.access-programmers.co.uk/forums/showthread.php?t=174579

Since the problem was in my tables, I thought I'd bring it over here.

I'm trying to build an application which will allow our project managers to put together estimates for their clients and to create work orders for our installers.

I think I've gotten things much more streamlined and I welcome any input. This is only the second time I tried building a database, and the last time was several years ago.

Thanks.

At first glance, I think you need to explore 1 to many relationships, especially for your jobs tables

From looking at the tables it seems unusual to have shade 1,2,3,4 and film 1,2,3,4

Surely there should be a shade table and a film table and then link to them in with keys?

From looking at the tables it seems unusual to have shade 1,2,3,4 and film 1,2,3,4

Surely there should be a shade table and a film table and then link to them in with keys?

The 1,2,3,4 refer to scopes of the job. Any given job can have up to 4 scopes (to start - I'll probably have up to 10 scopes for shade jobs when it's all said and done). There's a different set of criteria by which we price shades vs film which is why I have it broken out like this. I had initially had a separate table for each film scope and shade quote linked by a primary key, but I was having serious issues when I tried running a query on it which is what brought me to this board where it was suggested I bring those into the main job tables.