Search results

  1. S

    Field's Default from table other than Source

    Yes, that's better! Thanks again!!
  2. S

    Field's Default from table other than Source

    Wow! That code works great!!!! I will definitely have to remember the Dlookup function! Thank you very much Kiwiman, MSAccessRookie, and gemma-the-husky!!! I added a refresh command to refresh a subform I have at the bottom of my form. Here is all my code for this event in case it helps...
  3. S

    Field's Default from table other than Source

    Actually, I just got it to work by making a small change to the syntax: Me.strLossAddr = DLookup("[strInsAddr]", "tblInsured", "[sngInsuredID]=" & Me.sngInsuredID) This seemed to do the trick! I am storing my information as follows: a) the Claim table, which specifies the Loss Address...
  4. S

    Field's Default from table other than Source

    I typed the following for my namefieldinform After Update click event: me.strLossAddr = dlookup("[strInsAddr]","tblInsured","[sngInsuredID]= '" & me.sngInsuredID & "'") and I as I filled in my namefieldinform and tabbed to the next field I received the following Microsoft Visual Basic error...
  5. S

    Field's Default from table other than Source

    On a form, is there a way to make a default to a field that is from a table other than the record source's table? I am making an insurance claim form whose loss address is "typically", but not always, the address of the insured. The Field's record source is from a table called tblClaim, and the...
  6. S

    Table relationship: Bill & Fees tables

    I'm sorry, I see what I did, George. I had to allow duplicates of the lineItemID foreign key in the tblInvoiceDetail table.
  7. S

    Table relationship: Bill & Fees tables

    tblInvoice Pro# (Primary Key) Ship Date BOL# one-to-many tblInvoiceDetail DetailID (Primary Key) Pro# LineItemID one-to-one (?!!) tblLineItem LineItemID (Primary Key) LineItemName LineItemChargeAssuming I have this correct, any ideas on why I can't create a one-to-many relationship with the...
  8. S

    Table relationship: Bill & Fees tables

    So I now have: tblInvoice Ship Date BOL# Pro # (Primary Key) One-to-Many, tblInvoiceDetail InvoiceDetailID (Primary Key) Pro # AccessorialID One-to-One (?!!)...
  9. S

    Table relationship: Bill & Fees tables

    I think I've got the concept of how the form works, George, but what are the tables and their keys going to look like? I believe this is what I am struggling with.
  10. S

    Table relationship: Bill & Fees tables

    Okay, I'll check it out. Thanks a lot George!
  11. S

    Table relationship: Bill & Fees tables

    I don't think I completely follow you, George. From this I can only envision using several subforms, one for each line item that is included on the invoice, or using a single subform that itself will call on a table several times. I'm sure my scenario isn't all that uncommon but, just in case...
  12. S

    Table relationship: Bill & Fees tables

    What kind of relationship do I need between a table created for "bills" and one for "fees", where there can be more than one fee per bill. In the "fee" table there is a "Fee Name" and a "Fee Charge"? On the "bill" form I use a combo box and I would like to be able to add to the "fee" table...
  13. S

    Capturing Variable Monthly Fee in a Running Total

    I have to impose a single monthly fee on a billing report for each month that transpires and capture this fee as a running total on this report, which will eventually span the course of years. Understanding that this rate is variable, what is the best way to accurately capture this information?
  14. S

    Best way to maintain billing rate history?

    Thanks for your advice, neileg. I've posted this question in three forums and nearly everyone prefers the pragmatic approach. You mentioned that looking up the rate is hard. I was hoping to use a lookup for the Rate field on the Bill form that would call on stored rate information located in...
  15. S

    Best way to maintain billing rate history?

    Thank you very much for your valuable insight and advice, gemma-the-husky and David. I think I understand my options much better now! On one hand I could: Link a Rate History table to the Customer table via the Customer ID. In addition to the Customer ID foreign key, the Rate History table...
  16. S

    Best way to maintain billing rate history?

    I have created a table for customer bills, and a table for customer profiles which contains rates associated with them specifically. The problem is that after a new rate change has been imposed I want to be able to look at an old bill, via a report, and have it reflect the "old" rate within...
  17. S

    Guidelines Needed Regarding Charging Clients

    Those are some great ideas, guys, I will definitely look into them! Thank you very much!
  18. S

    Guidelines Needed Regarding Charging Clients

    Thanks Pat, I will definitely check out guru.com, right not my goal is to get experience and I am not expecting to make a lot doing this. (It is funny that you mention the Quickbooks thing, I have run into that exact experience already!! :) )
  19. S

    Guidelines Needed Regarding Charging Clients

    I hear you completely, however I haven't had much trouble getting work and the folks whom I have created databases for have been pretty happy. I think it has a lot to do with the fact that many companies, particularly small ones, feel that investing in IT personnel is still an unnecessary...
  20. S

    Guidelines Needed Regarding Charging Clients

    Since I left school I have had to jump into application design on my own because I am finding it difficult to find work without 1 to 3 years of experience typically required by the current job market. This leaves me without any gut feeling for how to charge my customers. Charging by the hour...
Back
Top Bottom