[AccessD] Windows 7 & Access 2007 (.mde) Caution Warning!!!

Robert robert at servicexp.com
Fri Jan 22 10:30:01 CST 2010


Rocky,
  I have one beta user on a 64 Bit machine. Everything related to Access
seems to be working OK. 

The reason why I say "related to access", is because I have quite a few
ActiveX Controls being used, and so far the only one that is giving us
problems is a external printer control..

 Isn't a P4 64bit??  If so, then you could move to 64 bit, providing the MB
manufacture has those drivers available. (and in some cases MS has them and
the MFG does not)...

 Just make a bare metal backup of the drive before you begin... ;-)


WBR
Robert




-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Rocky Smolin
Sent: Friday, January 22, 2010 11:16 AM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Windows 7 & Access 2007 (.mde) Caution Warning!!!

Different (but related) question - same thread:

I'm seeing some resellers on Ebay selling the full version of W7 (not the
upgrade) some are 32 bit, some are 64 bit.  I'm thinking of upgrading my XP
box which is a P4.  I need 32 bit, yes?

TIA

Rocky
 

-----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

-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com





More information about the AccessD mailing list