Jim Lawrence
accessd at shaw.ca
Sun Jan 24 11:18:10 CST 2010
Hi Robert: It seems to be in the order of installation... Access2007, then Access 2003 and finally Access 2007 again. Even though Access 2003 and 2007, are supposed to be able to co-exist this is not true. Each one will over-write files in the "C:\Program Files\Common Files\Microsoft Shared\Office11 and Office12" subdirectories and clobber or confuse them selves and the other. I played for a couple of hours to get them both to play nice on my development computer. I think if you want to get a perfect install your method might be the best... Uninstall 2003 and re-install 2007. Jim -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Robert Sent: Friday, January 22, 2010 7:59 AM To: 'Access Developers discussion and problem solving' Subject: [AccessD] Windows 7 & Access 2007 (.mde) Caution Warning!!! Ok, so you may remember in my earlier posts about my observations of the above. I mentions that I had never had a user corrupt a FE. Well, reports started to come in from like 8 of the 11 beta users with the EXACT same error. I spent pretty much all day yesterday, looking through my code, looking for a possible cause. The problem was, I could not create the problem on my 3 test boxes. So I started to look at the differences in the computer systems, and the one discernible difference was the: "Microsoft Office Access Database Engine 2007" Was installed on the effected Windows 7 / Access 2007 machines. The beta testers that did not have that problem, did not have this under installed programs. After un-installing the above along with the Access Runtime (I just did this for caution), then re-installing my program with the Access Runtime. The error appears to be gone. I'm not sure you really need to un-install the Access Runtime Engine, as I did this and re-installed, before realizing the Database Engine thing, and it made no difference in the error, it remained. The problem is, I don't know why / how this Database Engine is getting installed. It's removal doesn't seem to affect any of the office programs.. I'm a little concerned that it will get automatically installed again through updates.... Where does one go to submit this with the MS Access Team, because this seems like a "real hum dinger" of a problem...??? WBR Robert -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com