Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Categories

How to increase MS Access / VBA CPU usage.

I'm running Office Access 2003 on a Pentium 4 3Ghz with 1Gb memory. When running code in the modules section of Access, I can never get cpu usage above 50%-51%. It seems like Office has throttled itself not to use the cpu. Similar apps I've written in Access 97 run much faster. I've checked all over the net for an answer. Before I uninstall the 2003 version and go back to Access 97, I thought I'd post here to see if I've overlooked anything.

Basically I just have various vb code that iterates through recordsets adding or changing records. There can be hundreds of thousands or a million records depending upon the database or table involved. Access 97 can process around a hundred records a second and Access 2003 can process about 2 records a second, which isn't really viable for me. In Access 97 I can peg the processor. In Access 2003 it never goes above 50% or so. Seems like, somehow somewhere, Access or Jet is throttling it's cpu usage. I've tried simple stuff like increasing threads in the registry, but doesn't really attack the problem. Have I missed some basic configuration setting?

Thanks!

Comments

  • jbassmanpjbassmanp Member Posts: 160
    : I'm running Office Access 2003 on a Pentium 4 3Ghz with 1Gb memory.
    : When running code in the modules section of Access, I can never get
    : cpu usage above 50%-51%. It seems like Office has throttled itself
    : not to use the cpu. Similar apps I've written in Access 97 run much
    : faster. I've checked all over the net for an answer. Before I
    : uninstall the 2003 version and go back to Access 97, I thought I'd
    : post here to see if I've overlooked anything.
    :
    : Basically I just have various vb code that iterates through
    : recordsets adding or changing records. There can be hundreds of
    : thousands or a million records depending upon the database or table
    : involved. Access 97 can process around a hundred records a second
    : and Access 2003 can process about 2 records a second, which isn't
    : really viable for me. In Access 97 I can peg the processor. In
    : Access 2003 it never goes above 50% or so. Seems like, somehow
    : somewhere, Access or Jet is throttling it's cpu usage. I've tried
    : simple stuff like increasing threads in the registry, but doesn't
    : really attack the problem. Have I missed some basic configuration
    : setting?
    :
    : Thanks!
    :
    I'm not sure what you are trying to do but cpu usage is consider a negative. Generally the more usage the slower the responds of the machine. You want your applications to use the cpu but not to the extent that all else comes to a drag. the closer you get to 100% the more drag.... So don't look at that for your problem. It is using half of the computers cpu resources now that is a strong put. Check out your code or something else. Maybe you are using some routines that are not as efficient as it could be casueing a slow down in its processing. It happens.
  • dokken2dokken2 Member Posts: 532
    : : I'm running Office Access 2003 on a Pentium 4 3Ghz with 1Gb memory.
    : : When running code in the modules section of Access, I can never get
    : : cpu usage above 50%-51%. It seems like Office has throttled itself
    : : not to use the cpu. Similar apps I've written in Access 97 run much
    : : faster. I've checked all over the net for an answer. Before I
    : : uninstall the 2003 version and go back to Access 97, I thought I'd
    : : post here to see if I've overlooked anything.
    : :
    : : Basically I just have various vb code that iterates through
    : : recordsets adding or changing records. There can be hundreds of
    : : thousands or a million records depending upon the database or table
    : : involved. Access 97 can process around a hundred records a second
    : : and Access 2003 can process about 2 records a second, which isn't
    : : really viable for me. In Access 97 I can peg the processor. In
    : : Access 2003 it never goes above 50% or so. Seems like, somehow
    : : somewhere, Access or Jet is throttling it's cpu usage. I've tried
    : : simple stuff like increasing threads in the registry, but doesn't
    : : really attack the problem. Have I missed some basic configuration
    : : setting?
    : :
    : : Thanks!
    : :
    : I'm not sure what you are trying to do but cpu usage is consider a
    : negative. Generally the more usage the slower the responds of the
    : machine. You want your applications to use the cpu but not to the
    : extent that all else comes to a drag. the closer you get to 100% the
    : more drag.... So don't look at that for your problem. It is using
    : half of the computers cpu resources now that is a strong put. Check
    : out your code or something else. Maybe you are using some routines
    : that are not as efficient as it could be casueing a slow down in its
    : processing. It happens.
    :

    in theory, access 2002, 2003 is supposed to be faster and can handle a larger numbers of records. however, consider that access 97 has a smaller footprint and ran faster on less hardware. you might be in a situation where you are running the same hardware but the newer access version actually needs more RAM, faster CPU, etc in order to get optimum performance [WinXP/Vista may not even run on a 166Mhz cpu w/ 64MB RAM, but that cpu was quite capable to run Win95/98] the newer O/S or application will almost always need more hardware horsepower in order to run smoothly.
  • ponartponart Member Posts: 1
    : I'm running Office Access 2003 on a Pentium 4 3Ghz with 1Gb memory.
    : When running code in the modules section of Access, I can never get
    : cpu usage above 50%-51%.

    You probably have a Dual Core processor. Go to your System Device manager and look under processors. Are there 2 entries? MS Access is probably running 100% on 1 processor leaving the other processor to do other (minimal) stuff. You low record processing rate is probably due to something else.
  • rbsmith2000rbsmith2000 Member Posts: 1
    Did anyone find an answer to this? I have a similar issue with a resource-intensive sub-query situation on access 2003. The processor is dual core. If I could use more of the processor, I could reduce my 20 minute run time. TIA
Sign In or Register to comment.