Search results

  1. olorin

    Invalid use of Null in DlookUp

    I did go with Mark's in the end, but thanks for the pointer. If anyone else is looking at this post for solving the dlookup null thing, the functioning code is here Private Sub btnOK_Click() On Error GoTo ErrHandler 'check quantity is entered If txtQty = 0 Then MsgBox "Quantity cannot be...
  2. olorin

    Invalid use of Null in DlookUp

    Thanks for both recommendations, both worked obviously. Been out of this for a few years and it takes a while to get back into it. Thanks again
  3. olorin

    Invalid use of Null in DlookUp

    Hi, I have some code that I just can't get over the line Dim CompID As Integer 'look for component CompID = DLookup("ID", "tblComps", "Pnum = '" & Forms!frmGoodsIn!tbScanComp & "'") If CompID = False Then 'not found MsgBox "No component found, is this a new Component?", vbQuestion, "No...
  4. olorin

    Auto Format in Access 2007

    I'm getting the same problem when using Access 2007 in Vista. I don't know any technical work around. The only solution I have come up with is to design forms on a machine using Win XP and then put the Dbase on a flashdrive and plug the flashdrive in the Vista machine and use the import wizard...
  5. olorin

    Applying pkPersonID based on User LogonName

    Like it! Especially the personalised First Name touch. Thanx for the advice.
  6. olorin

    Applying pkPersonID based on User LogonName

    hi people, I have a module that runs when the Dbase opens. It grabs the windows UserName and places it in txtUserName on a hidden form. I also have a table for users: pkPersonID (primary key autonumber) First Name Last Name UserName etc The UserName field is filled-in using VBA when the Admin...
  7. olorin

    Question How to do calculation with columns?

    If you want to see calculated values based on database fields, you should create an unbound TextBox on the form as John suggests, or create a report based on the fields with an unbound control which does the calculations when the report opens. Calculated fields in tables are a big "no-no" in...
  8. olorin

    Question Should I or Shouldn't I

    Thanx so much for the logical reasons in all of your replies. I agree totally with all of them. It was only after I had deleted a couple, that I realised the value of solved threads. It would be good to have a section where solved threads can be moved to, so as to make it easier for novices and...
  9. olorin

    Question Should I or Shouldn't I

    Hi People, I started doing some housekeeping on my UserCp by way of deleting threads that were started by me, and that were solved. I deleted three of them and gave the reason for deleting as "Solved". I then wondered if I should carry on and delete the rest, or is it better to leave them on...
  10. olorin

    subform record selection

    Hi people, I have a form for entering details to generate a shipping note. On the form is a subform which updates when the user selects the product to be shipped. The subform shows all outstanding purchase orders for the selected product. Nine times out of ten, the purchase order to be used is...
  11. olorin

    Normalization

    Thank you so much for such a detailed response. Maybe I should give you some background as to why I developed the Dbase in the first place. I was given the position of looking after the shipping in the company where I worked. They had no database to track any shiping details at all! Only a...
  12. olorin

    Normalization

    Looks better to me. Although I do have a question. We make more than one product for single customers, and we sell the same products to more than one customer. So I made a junction table to allow for this, "jtblProdCust". The purchase order number we receive from customers may be for one product...
  13. olorin

    Assistance with creating tables

    An Excellent book on database design for helping people starting out with Access is "Grover Park George On Access" by George Hepworth. Reading that, will explain everything you need to know about designing a relational database.
  14. olorin

    Normalization

    Brilliant! Thanx for the tip. I will re-do the table relationships and post it here when finished. Then if you have time to look at it, I would appreciate any further tips. Thanx again for the advice.
  15. olorin

    Normalization

    Ahhhhh. I get your drift now. You mean a lot of the look-up tables that are linked could actually be just stand-alone tables, to refer to in combo boxes, and then store the selected data into the table that needs it. Wouldn't that amount to storing data more than once in the database? But there...
  16. olorin

    Normalization

    Thanx for the advice Ken, I also thought I had too many tables in it, that's why I asked for opinions, (all of which are gratefully received). As far as the Country Name in the Address table, I thought I had a look-up table, "tlkpCountry". Or do you mean a lookup field in the Address table...
  17. olorin

    Normalization

    Thanx for the reply Rabbie, how's this; tblPOrders pkPOrderID (primarykey autonumber) POnumber fkCustomerID (many side of a "one to many" link to tblOrganization) fkDelAddressID (many side of a "one to many" link to tblAddresses) table two; tblPOrderDetail pkPOrderDetailID (primarykey...
  18. olorin

    Normalization

    Thanx for the reply. So I suppose I only need the Order Number and CustomerID in the POrder Table, then everyting else in the detail table?
  19. olorin

    Normalization

    Thanx for your response. If I get your drift, you're saying that tblPOrders should be split into two tables. table one; tblPOrders pkPOrderID (primarykey autonumber) POnumber fkCustomerID fkProductID fkDelAddressID table two; tblPOrderDetail pkPOrderDetailID (primarykey autonumber) DueDate...
  20. olorin

    Normalization

    Hi people, I think I'm about done with Normalization. If any of you kind experts would cast an eye on the table structure (attached pic), and point out for me any pitfalls you see, I would appreciate it. Thanks p.s. I know tblShipments looks a tad large but a lot of the fields are Number fields...
Top Bottom