Welcome to SPN

Register and Join the most happening forum of Sikh community & intellectuals from around the world.

Sign Up Now!
  1.   Become a Supporter    ::   Make a Contribution   
    Target (Recurring Monthly): $200 :: Achieved: $98

proper structure

Discussion in 'Information Technology' started by Brian, Jul 28, 2006.

  1. Brian

    Brian
    Expand Collapse
    Guest

    We have a small manufacturing business. Most of our products are
    manufactured and delivered right to the customer; however, we occasionally
    make pieces to place in our showroom as displays but are sometimes sold to a
    customer.

    I am tracking the order and production of these items. Each manufactured
    piece is assigned an invoice number which is tied to a customer. For the
    showroom pieces, the customer = showroom, and the invoice# is a unique
    number different than the normal invoice#s


    (currently)
    tblCustomer
    -------------
    custID (PK)
    lastName
    firstName
    blah blah blah

    tblInvoice
    ----------
    invoiceNum (PK)
    custID
    Item
    blah blah blah

    What would be the best way to set up the sale of a showroom piece where it
    can be reassigned a new invoice number and customer. I was thinking of
    setting up another table like this

    tblSRSales
    --------------
    oldInvoice# (from the tblInvoice filtered for just the Showroom Customer)
    newCustID
    NewInvoice#
    DateSold
    blah blah blah

    If I do that, how would I differentiate the sold items from the current
    inventory in my reporting and queries?
    newCustID = null?

    Or is there a better - more efficient way?

    Thanks
     
  2. Loading...


  3. Tom Wickerath

    Tom Wickerath
    Expand Collapse
    Guest

    Hi Brian,

    Since you are wanting to maintain a transaction history, here is one
    approach that you might consider:

    Creating an Audit Log
    http://allenbrowne.com/AppAudit.html


    Using this method, you would simply change the CustID in tblInvoice and
    capture this change in the Audit Log table. Of course, changes must be made
    at the form level only, in order for the VBA code to be used.


    Tom Wickerath
    Microsoft Access MVP

    http://www.access.qbuilt.com/html/expert_contributors.html
    http://www.access.qbuilt.com/html/search.html
    __________________________________________

    "Brian" wrote:

    > We have a small manufacturing business. Most of our products are
    > manufactured and delivered right to the customer; however, we occasionally
    > make pieces to place in our showroom as displays but are sometimes sold to a
    > customer.
    >
    > I am tracking the order and production of these items. Each manufactured
    > piece is assigned an invoice number which is tied to a customer. For the
    > showroom pieces, the customer = showroom, and the invoice# is a unique
    > number different than the normal invoice#s
    >
    >
    > (currently)
    > tblCustomer
    > -------------
    > custID (PK)
    > lastName
    > firstName
    > blah blah blah
    >
    > tblInvoice
    > ----------
    > invoiceNum (PK)
    > custID
    > Item
    > blah blah blah
    >
    > What would be the best way to set up the sale of a showroom piece where it
    > can be reassigned a new invoice number and customer. I was thinking of
    > setting up another table like this
    >
    > tblSRSales
    > --------------
    > oldInvoice# (from the tblInvoice filtered for just the Showroom Customer)
    > newCustID
    > NewInvoice#
    > DateSold
    > blah blah blah
    >
    > If I do that, how would I differentiate the sold items from the current
    > inventory in my reporting and queries?
    > newCustID = null?
    >
    > Or is there a better - more efficient way?
    >
    > Thanks
     
Since you're here... we have a small favor to ask...

More people are visiting & reading SPN than ever but far fewer are paying to sustain it. Advertising revenues across the online media have fallen fast. So you can see why we need to ask for your help. Donating to SPN's is vote for free speech, for diversity of opinions, for the right of the people to stand up to religious bigotry. Without any affiliation to any organization, this constant struggle takes a lot of hard work to sustain as we entirely depend on the contributions of our esteemed writers/readers. We do it because we believe our perspective matters – because it might well be your perspective, too... Fund our efforts and together we can keep the world informed about the real Sikh Sikhi Sikhism. If everyone who writes or reads our content, who likes it, helps us to pay for it, our future would be much more secure. Every Contribution Matters, Contribute Generously!

    Become a Supporter      ::     Make a Contribution     



Share This Page