Search results

  1. D

    SQL String Returning Wrong Number of Records

    I think SJ's point is that you need to do a .MoveLast before .RecordCount shows the correct count. Dave
  2. D

    Runtime Error 5 in calculation. Driving me crazy

    Without checking this, it could be because you're using variants and passing in longs, so it's not converting the longs to doubles (or something). Try Rate = ((CDbl(vEnd) / CDbl(vStart)) ^ (1 / CDbl(vYears)) - 1) Dave
  3. D

    "." v "!"

    Ah, so that's it. Thanks for the explanation, SJ - clear as ever! Dave
  4. D

    "." v "!"

    I've seen numerous posts where posters are recommended to use one or other - I've always just used whatever felt right and never had any problems. What exactly are the pitfalls of using the wrong one? Dave
  5. D

    List Box - Freeze Columns When Scrolling

    You can do it with a datasheet view in a subform if that's any help... Dave
  6. D

    UK date headache

    Not nice though, is it? At least when you do it, it's all hidden away from the users in code & you can comment it to remind yourself! :)
  7. D

    normalization and relationships - don't know how to place data

    You need another table tblPaperSize, with PaperSizeID Name Length Width ... and a further table tblPagesPrinted, with PaperSizeID PrinterID Quantity ... Dave
  8. D

    UK date headache

    Date constants in SQL are always US format. You'll have to use docmd.RunSQL "INSERT into tbl_test([dates]) VALUES (#06/01/2005#);" Dave
  9. D

    Need a String Function

    Try updating to Format(CLng([Fieldname]), "000000") Dave.
  10. D

    Question about dates

    I think you'll either have to change the way you store your data so that if a period spans more than one month then there is one record for each monthly bit, or calculate the proportion of each period in the month you're looking at on the fly: it's a bit messy, but you might be able to do it in...
  11. D

    List for data entry

    It strikes me you'd have to enter a record for each property as at the new valuation date first (through code or a query). Once you're there, you can then filter to just those records and add the valuations through the datasheet view of a query, or (bettter) a form. Dave
  12. D

    Composite primary keys

    Thank you both - food for thought! Dave
  13. D

    Composite primary keys

    I've noticed that the great and the good all seem to recommend not using composite PKs. Does that even go for join tables in the middle of a many-to-many relationship? Not sure I see what's to be gained by adding an ID and making that the PK. Any comments? Dave
  14. D

    scrip error

    What is it supposed to be?
  15. D

    What phone(s) do you have?

    Now there's a thought! You could have a split database with the front end on a Bluetooth headset and the back end on the phone! :rolleyes: Dave
  16. D

    What phone(s) do you have?

    Oh dear, I'm almost ashamed to admit this... I've got an Orange SPV M2000 - branded incarnation of the HTC Blue Angel. It's got camera (still & video), internet (GPRS and WiFi), e-mail, Word, Excel, Outlook contacts & calendar, Media Player, MSN Messenger ... oh, and phone and SMS of course...
  17. D

    Update linked table definitions

    The one-off manual method is good enough for me! Thanks for your help. Dave
  18. D

    Update linked table definitions

    If a front-end database has links to many tables in a back-end database and the back-end is moved, is there an easy way to update all the table links in the front-end in one go, or do you have to set up all the links again one at a time? Hoping there's a quick way... Dave edit: just realised...
  19. D

    Rounding Down

    INT() will round down to the lower 1. Dave
  20. D

    merging rectangles

    So you need nearly what Doc Man suggested: Still the min of the Lefts and max of (Left + Width)s, but you need the max of the Tops and min of the (Top + Height)s. I don't think I'd describe what you've got as a "merged rectangle" though... Dave
Back
Top Bottom