Results 1 to 4 of 4

VBA Versus Macro

  1. #1
    RapidRepairArnold is offline Novice
    Windows 7 64bit Access 2010 32bit
    Join Date
    Oct 2012
    Kalamazoo/Battle Creek, MI

    Post VBA Versus Macro

    So I am trying to determine the main points for use of Macros and VBA. When I started using Access, I utilized Macros. It worked well for me since I had no real programming experience and Macro's appeared to be Newbie friendly. Now my database is starting to get slow. Someone (who, while smart, I would never believe over any of you) hinted to me that this could be due to the fact that I have many embedded Macro's running.

    I know ideally I should be using VBA. From what I understand, it is a lot more flexible and allows for greater customization of automation tasks. I am just looking for input on what you think. I notice most people on here use VBA, but why?

    And as a side question, does VBA actually load and run faster than a Macro?

  2. #2
    pbaldy's Avatar
    pbaldy is offline Who is John Galt?
    Windows XP Access 2007
    Join Date
    Feb 2010
    Nevada, USA
    I use VBA exclusively, due mainly to power, flexibility and error handling. I suspect it does load/run faster, but that's completely untested. That said, in the situation you describe, macros wouldn't be my first suspect. Have you traced the slowness to macros? Or could it be queries, forms loading slowly, etc.
    Paul (wino moderator)
    MS Access MVP

  3. #3
    RapidRepairArnold is offline Novice
    Windows 7 64bit Access 2010 32bit
    Join Date
    Oct 2012
    Kalamazoo/Battle Creek, MI
    I haven't, due to the fact that my database relies heavily on one table that has 700+ records, some navigation forms, and filtering based on some multi value selections. I eliminated alot of queries that, prior to deletion, did slow it down.

    I plan on getting bored in the near future and redoing it as a VBA coded database to see if it is faster. Just looking for the moral internet support to push towards doing it

  4. #4
    ssanfu is offline VIP
    Windows XP Access 2000
    Join Date
    Sep 2010
    Anchorage, Alaska, USA
    I too use VBA exclusively, also for the reasons posted.

    700+ records
    This is nothing for Access..... one of my tables has over 1.29 million records. My employee table has over 9,000 records.

    I would start with ensuring that the table structure is normalized.
    Check to see if the indexes are correct.
    No lookup fields . (different than look up tables)
    No multi-value fields.
    The evaluate the queries.

    Hard to say without being able to touch the dB. But that is where I would start...
    Good luck
    Last edited by ssanfu; 02-04-2013 at 11:34 PM. Reason: spelling
    "Veni, Vidi, Velcro"
    (I came; I saw; I stuck around.)

Please reply to this thread with any new information or opinions.

Similar Threads

  1. Fields show differently in table versus form.
    By zero3ree in forum Access
    Replies: 1
    Last Post: 08-01-2012, 03:58 PM
  2. Replies: 3
    Last Post: 08-04-2010, 09:35 AM
  3. Use of Lookup Column Versus Listbox
    By P5C768 in forum Access
    Replies: 2
    Last Post: 02-25-2010, 01:00 AM
  4. Access versus FileMaker Pro Advanced
    By genesis in forum Access
    Replies: 1
    Last Post: 08-20-2009, 01:00 AM
  5. dlookup versus SQL value search
    By marianne in forum Access
    Replies: 3
    Last Post: 07-15-2009, 09:23 AM

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
Tech Forums: Microsoft Office Forums