A new hot fix for Access 2007 is now available

Tony's Microsoft Access Blog — Thu, 01 Jan 2009 01:39:03 GMT

A new hot fix for Access 2007 is now available But I shouldn't have needed to tell you this on my

re: A new hot fix for Access 2007 is now available

CyrusB — Fri, 02 Jan 2009 12:22:39 GMT

Does anyone know if this hotfix can be rolled-back (i.e. without having to do a full re-install of MS Access)?

Thanks.

re: A new hot fix for Access 2007 is now available

Renaud Bompuis — Mon, 05 Jan 2009 10:05:35 GMT

Does this fix address the Runtime version as well? It doesn't seem to say whether it does or not in the notes.

re: A new hot fix for Access 2007 is now available

David Webb — Tue, 06 Jan 2009 20:06:54 GMT

I've just upgraded from Access 2003 to Access 2007. I have alread installed the latest hotfix (960307).

I have a front-end mdb with a few small tables in it, and most of my large tables are in a back-end MySQL database using linked tables and views in Access. The big performance problem, compared with Access 2003 (which was good), is with combo boxes in datasheets. Navigating a datasheet (whether seperately or in a Form) is extremely slow, like wading through treacle. If I convert all the combo boxes to text boxes then the problem goes away - but then I am looking at raw identifiers (index keys) rather than data a human can use (like a company name). The difference from Access 2003 seems to be that each time you navigate to a new record on the datasheet, Access 2007 performs a new query on the linked table for all combo boxes, whereas Access 2003 was smart enough to re-use the previous recordset since it "knows" that the lookup table for the combo box probably hasn't changed. That's my guess anyway.

Please can you let me know whether you are aware of this problem and if so what you are doing about it. It spoils an otherwise good product.