Results 1 to 2 of 2
  1. #1
    3 Star Lounger
    Join Date
    Jan 2001
    Wetherby, Yorkshire, England
    Thanked 0 Times in 0 Posts

    Code in Access 2k (A2K )

    Since changing all of my macros to code in my database it seems that the db has slowed down and leaves me with loads of temp files in my temp directory. The files are in the format 'wiz123.tmp', where the 123 can be any series of numbers and I get about 50 of them if I do any work on the db.
    It only started after I wrote the code, I,ve compiled and checked it myself word for word but can't see anything wrong.
    I was under the impression that code was faster than macros and in specific processes it seems to be, but the actual general running of the db is slower (screens take longer to clear and forms sometimes open like a slow blind being lowered)
    Any thoughts anyone?
    Peter Herworth

  2. #2
    Plutonium Lounger
    Join Date
    Dec 2000
    Sacramento, California, USA
    Thanked 1 Time in 1 Post

    Re: Code in Access 2k (A2K )

    There's no reason for an Access database to create a bunch of temporary files unless you're doing something specifically that generates them. If you create a new database and import all the objects and set the proper references, do you get the same behavior? If so, then it's something you're doing, and you would have to give us some sample code to get any useful answers.

    Code is *not* necessarily faster than macros. However, it is far more powerful and flexible and it allows you to trap and handle errors, which macros don't. <img src=/S/hmmn.gif border=0 alt=hmmn width=15 height=15>Do you have Name AutoCorrect turned on? If so, turn it off and see whether that makes a difference. Was this database created in Access 2000? If so, and if you have a lot of established relationships among tables (or implicit relationships created by table lookups), you will pick up a performance gain by turning off SubDatasheets as well. They may look useful, but they sap the performance of the database. Unfortunately, they have to be turned off for *each* table, although there is code to do this in the on-line help.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts