Thursday, December 09, 2010 11:34 AM
I have used Access RunTime 2002 on Windows Xp and Windows 7 for a long time.
After I've installed Office 2010 Professional Plus, in my ade program which runs Access 2002 Filter By Selection (Filter By Form) does not work anymore - nothing happens.
I removed Office 2010 and reinstall Access 2002. But the problem remains.
I removed Access 2002 RunTime and installed Office 2002,
still filter by selection nor the code works:
Monday, December 20, 2010 8:37 PM
I am experiencing the same issue. I have a program running Access Runtime 2003 and after I installed Office 2010 Professional Plus, I noticed the form filter stopped working. Have you found a solution?
Wednesday, December 22, 2010 6:22 PMModerator
Now that you are running a full version of Access 2002, what happens if you create a new .adp, a new form and then try to run the code to filter the form?
In the new .adp file and your previous .ade file, do you see (filtered) listed to the right of your record navigation buttons?
You mention that you are working in an .ade, do you have the original .adp file and is that experiencing the same issue?
Microsoft Online Community Support
Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Wednesday, January 12, 2011 1:53 AM
I am experiencing the same problem as Matjaz .
The filtering works on my .ade prior to installing Office 2010 Professional Plus.
When running the .ade file with Access Runtime 2003, the (filtered) appears when I run .Filter = 'UserID=123' .FilterOn = true and disappears when I run .Filter = '', except nothing is filtered.
I tried running the .ade file with Access Runtime 2010 and the filter works, but I cannot use Office 2010 as I have 3rd party controls in the application which is not compatible with Office 2010.
Can you offer me any help?
Wednesday, January 19, 2011 3:05 AMI have this exact same issue on a Windows 7 machine used primarily for development. Have a major Access Project done in Access 2003, after installing Office 2010 trial to help someone else with their development problem my form filters no longer work, and my project has a lot of them. The form filter still works in Access 2010, but no longer in 2003. We haven't migrated to Office 2010 yet, and problems like this will only put that off longer, so sticking with 2010 is not an option at this point in time. Tried removing Office 2010, re-installing Office 2003, with no luck. Tried creating a new simple .mdb and adding form filter, it didn't work either. Obviously Office 2010 is changing something that is breaking the form filter behavior in Office 2003. Without a fix I guess I'm stuck rebuilding the machine.
Wednesday, March 16, 2011 3:57 PMBumping this issue as I'm experiencing the same thing. Has anyone had any luck resolving the problem?
Thursday, June 16, 2011 2:54 PM
Has someone a solution for this problem already? I have the same problem on several maschines.
Atleast can someone from Microsoft confirm this is an known issue?
Tuesday, June 21, 2011 12:45 PMWow, I was surprised to find others experiencing the same problem with their Access apps that I'm experiencing. After installing new 2010 versions of Access / runtime, filters stop working within my Access (2003) applications. Any solutions yet?
Wednesday, June 29, 2011 11:00 AM
I just installed SP1 for Office 2010 in the hope this will fix this issue. But the problem is still the same. Filter is still not working!
any more ideas for a solution?
Monday, July 18, 2011 4:40 PM
Office 2003 ADP no longer filters after installing 2010.
- UNINSTALLED 2010
- REINSTALLED 2003
- Ran updates for 2003.
STILL will not filter.
Tuesday, July 26, 2011 3:09 PM
10.0.6776.0 Mscdm.dll 10.0.0.6712
Above .dll fix this know bug :
Records are not filtered in a form when the FilterOn property is programmatically set to True
When you programmatically set the FilterOn property to True in an Access 2002 form, the form does not filter the records. Therefore, the form may continue to show all the records.
I had exactly the same problem as every one on this thread. Installing 2010 Access runtime broke down my developpement pc ! downtime 6 days ...
mscdm.dll is the GUILTY one !
version of this dll on my pc after uninstall of 2010 was still 14.0.4731.1000
version of this dll on some co-worker pc 11.0.8164.0
and the article says that any newer dll is ok ... but it dont !
C:\Program Files\Fichiers communs\Microsoft Shared\MSClientDataMgr or for english OS
C:\Program Files\Shared files\Microsoft Shared\MSClientDataMgr
Temp Solution for the common user who wants to get its old 2002 running is to rollback mscdm.dll to whatever version was working before ! For me its 11.0.8164.0
Solution for microsoft is to fix 14.0.4731.1000 to ensure it dont breaks 2002 runtime, for us developpers who needs to deploy both 2002 and 2010 to customers !
And if a fixed dll exist, I sure wish to try it !
My next step is to reinstall and see if 2010 runtime works great with older dll... but I have some doubts that it will FULLY work. It may crash elsewhere ...
[edited] Tested 2010 and it wont work with the older dll in place ... thats logic ehhh ! ... [/edited]
At least, my access 2002 developpement environnement is now working !!!
For the benefit of everyone having this bug : please let me insert some french ans english keywords to this social article seen 1731 times as I write this solution
form filter doesn't work anymore
filtre sur le formulaire ne marche plus
form filter does not refresh
filteron = true
le filtre ne s'applique plus sur un formulaire
access 2010 runtime et complet avec 2002 co habitation
- Proposed As Answer by A. Bouchard Tuesday, July 26, 2011 3:09 PM
Wednesday, November 30, 2011 9:34 PMI am also seeing the same issue. I have several applications utilizing the Access 2003 runtime deployed to hundreds of users. After we upgraded to Access 2010, the Filter by Selection now longer works. Is there any chance that there will be a fix to this issue soon?