none
Microsoft Access Database Engine 2010 Redistributable - Resource Requirements

    Question

  • We are trying to use a DLL created in Visual Studio by one of our vendors in one of our internal web applications. 

    The DLL relies an an Access database (*.accdb).  The previous version of the DLL used an earlier version of Access (*.mdb) and we did not have any problems. When we changed to the new DLL and Access database we started having timeout issues.  The records that are processed appear to be correct but when we try to process a full day of records the times out. 

    We have 2 locations that need to use this new DLL.  We were able to get it to work at one location when we revised the memory constraints for the web site's application pool to 1024.  But this didn't work for the second location and we are not sure what other changes are needed.

    We would appreciate some suggestions or tests that we can perform to determine what is causing the problem.

    Friday, August 02, 2013 8:49 PM

Answers

  • ACCDB's cannot be locked down by the vendor. What problems do you encounter when you run this in the immediate window:

    Currentdb.Tabledefs("myTable").Indexes.Count

    (Of course you replace myObjectNames with yours)


    -Tom. Microsoft Access MVP

    Tuesday, August 13, 2013 4:04 AM

All replies

  • I would run the query in Access itself to see if it is slow there as well.

    If it is, standard database performance guidelines apply. Indexes, for example. Plenty of resources if you Bing for it.

    If it isn't, the slowness is not due to Access but to processing of the app itself or the bandwidth to the webserver.


    -Tom. Microsoft Access MVP

    Saturday, August 03, 2013 4:01 AM
  • Thank you.  Unfortunately the database, and the dll that uses it, are locked and we can't check for indexes, etc.
    Monday, August 12, 2013 7:45 PM
  • ACCDB's cannot be locked down by the vendor. What problems do you encounter when you run this in the immediate window:

    Currentdb.Tabledefs("myTable").Indexes.Count

    (Of course you replace myObjectNames with yours)


    -Tom. Microsoft Access MVP

    Tuesday, August 13, 2013 4:04 AM