Search results

  1. T

    frequently running an update query

    Hi Stephen, While you can convert your AutoExec macro to code, it won't work the same (the code won't work like the macro). Microsoft designed Access to have the AutoExec macro "do its thing" when the database is opening. There was no provision for an AutoExec module to affect the startup...
  2. T

    frequently running an update query

    Hi Stephen, You're right, the AutoExec macro runs when the database is opened. From the AutoExec macro, I call the Code I want to run (RunCode). I haven't used the Windows Task Manager to open the database. Rather, I've used a Scheduler Utility available through Dev Ashish's Access Web Site...
  3. T

    frequently running an update query

    Stephen, While you can run an update query once a minute, it's not the wisest thing to do. If you run the update query for more than a minute (it can happen - I've had some take that long and longer), then your plan to run once a minute become troublesome. Also, because Access macros do not...
  4. T

    pointer finger

    Screen flicker Amy, Just spotted the following on the Microsoft Knowledge Base (MSKB) - about screen flicker in Access 2000. It's about a third of the way down the page. You can find the article (Q210178) here. Display Problems When Scrolling Through the Employees Form in Northwind...
  5. T

    pointer finger

    You're welcome! What you did was tell Access the following: when the Pointer goes over a Label (Label's Mouse Move event), change the Forecolor to the value shown. Unless you tell Access anything else about the label, its Forecolor will stay the same. So you told Access when the Pointer moves...
  6. T

    pointer finger

    Amy, You might try something like this (code behind the form): Private Sub Detail_MouseMove(Button As Integer, Shift As Integer, X As Single, Y As Single) Label24.ForeColor = QBColor(15) Label25.ForeColor = QBColor(15) End Sub and these: Private Sub Label24_MouseMove(Button As...
Back
Top Bottom