Search results

Well, what I am trying to handle is that an 'Entity' (in the case it is a company) might have multiple employees who are simply 'Authorized Buyers'. This means that let's say that the Entity is Steven's Plumbing and I have my technicians John and Jack who works for me. John and Jack both has the...

Yes, I will go along with your term of speculative project. I call it 'Work Order PRO'. A long time ago I build a very basic version of the same thing, but, I want to totally start from scratch and think outside of the box more. It has been over a decade since I did that. What I do remember is...

Maybe I was not clear from the beginning. There is not an existing business, so there is no existing business rule. I am creating a DB with what I am going to call 'core features' that I can build off of when a new client wants to buy the DB, I want to have 'something' to promote to potential...

OK, I read what you said here and thought it through some more and took what you said about the TransactionT table and decided to put it back because there ARE uses for it, such as SALES, PAYMENTS, REFUNDS, and ADJUSTMENTS. If you notice by the relationships diagram I have added a SalesOrderT...

I guess the other way would be to eliminate the transaction table altogether. I could just include ALL the fields in the JobT table that I would need in either situation and then using just buttons, queries and screens to present the user with what they need, either just a single work order on...

First of all, YES! You do want a person to come back for repeat business. I actually started out the way you described with the criteria of; A customer can have many jobs and, Each job can have many work orders So, there was the Entity table Job table and Work Order table I guess the...

Here is a picture of my relationships of my database. At the top left you will see that there is an "Entity" (The Customer). They make a transaction. One type of transaction is just a single work order to do a small job, such as going to someone's house to fix their sink. The second type of...

WOW! Hey, everyone! What a lively conversation this has turned out to be and a very, very informative one as well! Thanks so much to EVERYONE for your insights on this topic and it helps a lot! I want you all to know that YES! I did take the time to read everyone's replies here and while I am...

Yes, your right. One of my thoughts is that since this is a Work Order DB that there will be a another table to store the names of other people who work at the customers company who might call in to place a purchase order to track who is authorized to place purchase orders as well as other...

Yes, sounds good..

Point Taken! Thanks for that ..

Access defaults field size to 255. Can anyoneplease shed some light on the importance of this property and how to set it right? What happens if I don't change it? For example, a field for the 2 letter code for STATE does not need 255 charcters! Is there a benefit to changing this property?

Work Order database, so I don't need personal details about oeople to that degree. It's mostly for business purposes.

I hear you. The video that I was referred to earlier looks cool. It goes into much deeper detail of database design theory than I have seen before which is really helpful. So, jdraw, thanks for referring me to that!

Good Question. I wrote a Work Order Database previously, but it was quite basic in nature, so it is my intent to expand and improve on that, starting with trying to streamline (I guess that is the right word) the number of tables I use and try to learn a lot from my previous experience with...

What I mean is, for example, the extended details for a PERSON might include things like birthdate, Social Security Number, State ID # (Drivers License or State ID, etc.) and so on about an individual. The extended details for a contractor might include things license #, ServiceID (Can select...

I am literally at the very beginning of my database planning. As a result of another thread I got turned onto an article with some interesting ideasfor database structure so I decided I am going to use at least part of it. So, to have less tables, all customers, vendors, contacts and anoth...

So, I took a look at the link provided by jdraw called ' reference' that has all the diagrams of the database tables, etc. For me, it is packed with tons of good ideas! FOLLOW UP QUESTION: As far as in the example provided it called all the people/companies/contacts, etc..... Party.... OK...

Thanks to EVERYONE ! I am new here to this forum and looks like it might be a source of some great information. The good news is that I am just in the beginning stages of my DB and can very, very easily implement some of your great ideas and information! With gratitude, -Steven

Hi: Doing what I am asking below will be a brand new skill for me to learn! I am in the beginning stages of developing my application. So, for this example I am going to use CUSTOMERS. So, the beginning of my customer table looks like this: CustomerID FirstName Middle LastName In also have...