There is a frontend and a backend database.
The frontend database is installed on a couple of machines.
You open the frontend, a form opens with a list box, the list box is created by a query.
You can double click on an item and it opens fine.
As SOON as the updates are installed and you open the frontend database and database and click on an item you get the error.
Then you uninstall the updates. Open the frontend database and it works again.
I tested it on XP VM machine and on another (offsite) machine. Same problem.
I already did the fix and repair database.
The references I have in MVB -> Tools ->References Are
- Visual Basic for Applications (c:\program files\common files\microsoft shared\VBA\VBA6\VBE6.DLL)
- Microsoft Access 11.0 Object Library (C:\Program Files\Microsoft Office\OFFICE11\MSACC.OLB)
- OLE Automation (c:\windows\system32\STDOL
- Microsoft FlexGrid Control 6.0 (SP6) (c:\windows\system32\MSFLX
- Microsoft Common Dialog Control 6.0 (SP6) (c:\windows\system32\COMDL
- Microsoft Active X Data Objects 2.8 Library (c:\Program Files\Common Files\System\ado\msado15.d
Main Topics
Browse All Topics





by: LSMConsultingPosted on 2009-03-12 at 03:42:43ID: 23866659
Does this happen on ALL your machines running this database?
The KB articles you reference involve the SMB service, and an update to the ActiveX control engine specifically regarding two controls ... unless you're using those controls, they should have no effect on you.
The first thing to do would be to insure that you don't have a corrupt database. Make a backup of the db, then click Tools - Compact and Repair.
Open the VBA Editor, click Tools - References. Are any marked as MISSING? If so, then you need to fix this issue - either find and reference the correct files on the machine, or install the necessary programs.
Again open the Tools - References dialog, uncheck any of your references (note the name and location of this reference), close and reopen the dialog, and then recheck that reference. This forces Access to rebuild your references.
Still in the VBA Editor, click Debug - Compile and fix any errors you may find.
Finally, do a Compact and Repair again.
For the record, I haven't heard of anyone experiencing issues after installing those two updates. Also, the second indicates that it will be added to a Service Pack, so I'd assume you should get this fixed before then.