access runtime bugs

This page is intended to show a few bugs/flaws happening using access 2007 and 2010 runtime AND windows 7 (SP1 and non-SP1). This is of course not exhaustive but it is sometimes a BIG bug. These flaws don't happen using win xp pro sp3 or win vista sp1 concerning access 2007 runtime v2 (access 2010 runtime has not been tested on vista / xp). The tests have been done in 3 environments, each time opening the same database:

Configuring test environment


The following registry keys have been added (14.0 for runtime 2010, 12.0 for runtime 2007):

Tests and samples are done on the .mdb file (not the mde), holding code and tables. The file format is access 2000 (as some users still use access 2000), and converting to last format didn't help anyway.
The registry keys have been added with and without the \Wow6432Node in the path, on access 2003 only setting security low was needed.

problem 1: continuous form with DCount and DLookup (2007 runtime)

If you have a continuous forms with in the detail some zones with ControlSource "=dcount(...)" or "=dlookup(...)", the zones are not computed on a2K7 runtime (if you are on win 7 sp1). This problem also occured on vista and was fixed by installing vista sp 1. On slow computers (virtual machine on a mac for example), you have the screen flickering every one minute (seems refresh is done on display by runtime 2007).
access 2003

 access 2007 runtime

 access 2010 runtime

On access 2007, the counts appear only (in detail and in footer):

Here is a sample to reproduce the problem. Strange, if you change the name of the field on the form [ID traitement] to [ID_Traitement], and do it also in the query ReqCountSéanceD, it works better, here is the patch. Would it be related to spaces in field names?
BUT the problem is not really solved:
  • if you wait a few minutes, the zone become white again
  • it is not only a display problem: if the code takes the value property of the control, it is null while it is not computed.
  • Sending an F9 key via sendkeys doesn't solve this correctly, f9 has to be repressed every minute and after each scroll
  • Here is another sample, just click button below screen.
    MicroSoft support told me about known problems with DCount and DLookup and access 2007, and that an access 2007 sp3 / runtime v3 should arrive soon. However, I am able to reproduce such a problem using a recordset, without dlookup/dcount. It also happens if a zone from another form (background, even not hidden) is used to compute the expression (for example, if you filter on a zone from top form).
    Waiting!!!!!!!

    problem 2: footer becomes header (access 2010 runtime)

    Suppose you have a continuous form without header, a detail band and a footer. If you open this form on no data (empty table), footer goes top and buttons begin to move alone from top to bottom (2010 runtime was tested, really????).
    access 2007 runtime

    		 access 20010 runtime

    Download sample!, just no data in table and move mouse over buttons.

    problem 3: error on Like with accentuated characters

    In the following sample, type "Clé" in the text zone then "Rechercher" (search). It runs a query filtering where a field is like "Clé*".

    Only 2 values are filtered but 8 names begin with Clé in the table. You can see it immediatly when running the query "Bugged", the parameter is in the like.
    I couldn't find any reason explaining why 6 rows were not displayed and 2 were. This happens with any access version. It seems to be related with index and non-English character in a text field:

    problem 4: (bug or feature?) No export from a report to word

    Using access, if you preview a report in run-time mode, you have a button in the toolbar to send it to word, where you can modify it. This icon is not present in access run-time, even is word is bought and installed, and can't be added because toolbar cannot be customized (this is something that was feasable with access 2000 runtime, but I couldn't find a way to customize toolbars and display them in access 2007). It is perhaps a feature (so not a bug), but the user loses one (important) functionnality.
    Is there a way to add it?

    problem 5: access runtime 2010 64 bits

    I wasn't able to run any application after installing access runtime 64 bits on win 7 pro 64 bits (always an error at startup). No problem when replaced by runtime 2010 32 bits. Should I compile mdb on 64 bits?

    Problem 6: If access 2000 is installed

    Starting access 2000 will reset the access 2007 sandbox mode to value 3, causing macros not to run correctly. Strange to see an older version changing config of a newer version!

    problem 7: on win 7 64 bits, mdb has to be compiled with access 2007

    To reproduce the problem, start access 2003, create a blank database, put a table in it, then copy it to a machine where access 2007 runtime is installed.
    Double clicking the file will cause a gpf when starting runtime if it is on win 7 64 bits (and that will not happen on win 7 32 bits). Open file with access 2007 32 bits (using network), close it, you can reopen it using runtime on win 7 64 bits without error, "great"!

    problem 8: buttons inside a frame cause screen flickering (access 2010 runtime, this is perhaps normal, showing control focus?)

    If you put buttons inside a frame, The screen flickers everytime the mouse goes over the buttons. Doanload Sample!