Search results

  1. LPurvis

    Search in recordset

    And to be clear, I wasn't advocating anything. Just stating eventualities. Naturally, records wanted in a specific order should be requested in that order. (Even if they're wanted in primary key order.)
  2. LPurvis

    Search in recordset

    As far as I'm concerned, nothing I said is contradicted there. I stand by what I said. Note, I said records are returned. (Not stored.)
  3. LPurvis

    Search in recordset

    Hi all. Random thoughts as they pass through my fingertips (having bypassed my brain of course!) Unles otherwise specified, records should be returned ordered by the primary key - though it's true they aren't necessarily stored in that order (unless you've just compacted the database)...
  4. LPurvis

    Object required after transfering code from form to module

    No worries. Little things are easy to miss.
  5. LPurvis

    Object required after transfering code from form to module

    Hi, welcome to AWF. Can you confirm that you're getting a compile error or a runtime error - and which line it's pointing to? The Open method or some reference to a URL that you were making? I notice in your code that you end up with a output.Value = oXMLHttp.responseTextwithout declaring...
  6. LPurvis

    ADODB RecordCount

    Blah? It depends greatly on the content of the Blah. Directly as above (i.e. a Keyset cursor) there should always be a RecordCount available. It depends on "Blah" and what you mean by "useless".
  7. LPurvis

    move to next record of a subform on a tabbed form

    Hi A very natural request to avoid the onscreen movement. Assuming you're using Access 2000 or newer (a safe assumption these days surely ;-) you can access the form's recordset property and accomplish the above with a single line of code. Me.frmDOC.Form.Recordset.Movenext Cheers.
  8. LPurvis

    Persistent connection to backend

    Are you using linked tables in this Access application of yours? If so - it's worth considering having a simple or even dummy table in the BE that you hold a recordset open to - so that the connection that is persisted is the same one your linked tables are using. You could repeatedly open...
  9. LPurvis

    Edit ADO Recordset

    A few questions spring to mind. First of all - storing a value in another field based on the autonumber field value is textbook data redundancy (violating normalisation). Do you even need to do this at all? What purpose does it serve? What's the source of this data? An MDB/ACCDB file (aka...
  10. LPurvis

    Please read Masters of Access VBA

    Seriously? That's your response?
  11. LPurvis

    Please read Masters of Access VBA

    Doug Steele covers drag and drop emulation in Access in an article from... a while ago. http://www.accessmvp.com/DJSteele/SmartAccess.html You'll need to invest some time and effort - it's not at all inherent functionality. Cheers
  12. LPurvis

    ado parameter query

    Started answering it over the way here :-)
  13. LPurvis

    Pass Through Query Report

    Yes a report in design view has no option but to execute the passthrough to obtain the definition - as, unlike liinked tables, there's no way that the schema can be cached (it can be an ad hoc query which could even return different columns each time it runs!) Perhaps surprisingly though...
  14. LPurvis

    How to get rid of non - alpha-numeric characters?

    I'd agree - the shorter the better. Hence why I'd probably view returning multiple spaces as a result of the Reg Exp replace, and so something to be subsequently handled. (Otherwise the expression becomes more and more unwieldy - as you've found. ;-) For example (and again I don't know if...
  15. LPurvis

    How to get rid of non - alpha-numeric characters?

    Heh, I wouldn't exactly say I'm getting in on it. (Such time elludes me at the moment.) Just thought I'd throw out something I'd previously done. I'll leave you to your lengthy expressions. It looks like you've got a solution anyway... Cheers.
  16. LPurvis

    variable length gets cut off

    That would be the ish factor. ;-)
  17. LPurvis

    variable length gets cut off

    Hi Bob. 1024 ish characters but yes - it's limited. Though it seems the implication is that it's not down to this testing methodology. We'll see.
  18. LPurvis

    variable length gets cut off

    I understand the scenario you're decribing. But we'd really need more to go on than that. For example, the details of the two functions. i.e. how the second one uses the same variable as the first - and exactly how you've determined that it is truncated (where is that tested and what is the...
  19. LPurvis

    variable length gets cut off

    Hi Paul My first rule of debugging - eliminate the discrepencies. Eventually you get to Sherlock Holmes old axiom (often repeated in modern media - in shows such as CSI). "When you have eliminated the impossible, whatever remains, however improbable, must be the truth" I find that hard to...
Back
Top Bottom