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

Robert robert at servicexp.com
Fri Jan 22 12:04:40 CST 2010


They did make then though... Right??

http://www.hardwaresecrets.com/article/105


WBR
Robert


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

Is a P4 a 64 bit processor?  I don't think so.

John W. Colby
www.ColbyConsulting.com


Charlotte Foust wrote:
> You could upgrade to 64 bit.  It will require a clean install regardless
from XP, so it's up to you.  
> 
> Charlotte Foust
> 
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Rocky Smolin
> Sent: Friday, January 22, 2010 8: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