Recent content by focus12321

Wait, dont even look at this, I already see at least one problem

Alright I have been working on this the past couple weeks and went through a ton of different versions. I think I'm on the right track... But I am stuck on a cascading combo box. I have the first two combo boxes working but cant get past the next one. If someone could look at what Ive created...

Thank you for your help. Yesterday I spent about 7-8hrs watching tutorial videos, after seeing some of this stuff all the way through I started getting it a little more. I now see why you (and Spike :) ) are saying to use one table for items. I'm going to rework my DB and I think I can come up...

I may have used terms loosely and made this all a little confusing. I'm not sure if it makes senses in a DB to keep items and labor completely separate but they need to be reflected on the invoices in completely different spots. Hence what I made separate tables. ... now for structure I think...

Ive been inputting a bunch of trial data, its helping understand the data, but I still think I might be having issues setting up the relationship to items and there prices and trying to relate the Invoice or fieldsheets. On each invoice is a jobnumber or "JobID" I need some relationship to say...

I'm not trying to be indecisive. Im not understanding what to do to fix the circular problem you are referring to. Item, is my materials. Sheet = daily field sheets which become billable. So if a tech went to a job and was there for 3hrs I can bill for it. But the client needs to know what...

Thank you for giving this a look. The suggestions you made I will probably do in the next couple days, they seem to make sense. (With the exception of the middle-initial, I'm really just trying to mimic our current system so I can create an ODBC in the future possibly). Now to the...

Attached is my current database. Just to be clear on how workflow happens. We have clients with contracts (jobs) and because there are these contracts the pricing for material and labor hours are specific to the job. There are a lot of maintenance jobs, with these we have "field sheets" that...

Please look at my attached file and see if these relationships look right. Id attach the file but I now need to start from scratch. I'm going to add the Primary Keys to all be autonumber as suggested. The relationship/table im most concerned with is the one for "pricing" as you can see I...

Will do, spike second day in a row youve helped me out! Thanks!

Let me preface this by stating this is only my 3rd day working with access. Seeming to understand what I need, and what tables to create. Already have a lot of what I need to get this project in motion. I am trying to build an invoicing database for maintenance invoices. I have typical items...

Sorry just want to clarify this, but pretty sure I get it. So even though the primarykey would be an auto number the way all the other tables interect with this table would be the foreign key (possibly my job number)? TblCustomer ------------- CustomerPK (autonumber) CustomerFK (number) <--...

Hm, if it should never be seen by the end user (makes sense) maybe I should just use a ID (autonumber) then our job number in the following column (row) whatever you want to call it. Probably best.

Sorry but I am unfamiliar with UOM?? Also each customer doesn't have a "discount" they have specific pricing for different items. I believe spikes comments have helped with this. I now have a working price list, or at least it seems that way lol. Now one last thing with this, is it really...

If you could only see the pad of paper in front of me. Exactly what Ive been doing. LOL Thanks. I dont mind going in and updating pricing throughout the contract, its only a few of them and only happen a couple times. Id be more worried about keeping the old invoice prices the same.