microsoft.public.access.tablesdbdesign | Forum profile

  Thanks for the John, There definitely are multiple items per invoice. My table structure is the following: Invoice table > transactions table > products table. Multiple transactions per table. Can you describe a little bit further your statement "InvoiceDetails table typically - you can do so in the afterupdate event of an item combo box, or some other appropriate event." also if you have an example...

  in nutting through this myself i'm thinking this can be fixed by creating a totals query for the search field but this doesnt work and i get this error You created an SQL statement with an ALL, DISTINCT, or DISTINCTROW predicate and an ORDER BY clause that contains a field not listed in the SELECT statement. Remove the DISTINCT reserved word, or remove the specified field from the ORDER BY clause. i'm not really good with...

  On Mon, 2 Nov 2009 17:41:01 -0800, deb <deb@discussions.microsoft.com> wrote: >now my lookup/search combo box is duplicating all the records because of the >car parking spaces Then correct the errors in your form or query design. If you would like help doing so please post the structure of your tables and your form. -- John W. Vinson [MVP] .  

  >>They then close out the form and the table is updated with the information that they entered. I asked how this is accomplished. If you post that information I may be able to tell you how to modify it so the rest of the data is passed. Do you have a one-to-many relationship between the two tables? -- Build a little, test a little. "Brent Sweet" wrote: > Hi Karl, > > Ok So...

  It's going to be pretty much work if the SSN must be hidden from all other users. Also you won't be able to use it as the primary key field. Note: using a SSN as the PK is a bad idea anyway. What happens if you have an employee who is not a US citizen and therefore doesn't have a SSN? 1. You'll need to implement user-level security. Note that Access 2007 accdb files do not support user-level security. 2....

   

  plisvb, I would have... tblInvoice iInvoiceiD (PK) iDate iCustomerID (FK linked to PK in tblCustomers) etc... tblInvoiceDetails idInvoiceDetailID (PK) idInvoiceID (FK linked to PK in tblInvoice) idQuantity idUnitOfMeasure (Optional field) idGroceryID (FK linked to PK in tblGroceries) idDescription idPrice idBackOrdered (Optional field) idApplyCoupon (Optional field) tblGroceries gGroceryID (PK) gItemID gBrandID (Optional field)...

  Hi Karl, Ok So basically form 1 has information about the customer, then we click log interaction which brings up form 2. Some of the fields such as member ID are carried over from form 1. Then the rest of the fields are entered by the user interacting with the customer manually. They then close out the form and the table is updated with the information that they entered. The problem we have is the things passed from form 1 to form...

  Gina, Did you mean that: - you never use a query as one side of a relationship? or - you never create relationships in the query design screen? Thanx Fred