[AccessD] Article on stuff broken in Access 2007

Edward S Zuris edzedz at comcast.net
Thu Jul 3 15:27:32 CDT 2008


 FWIW, For What It's Worth.  Someone in sales, somewhere,
 is talking to clients into upgrading to Access 2007.

 In one way it is a pain, unless a client has a budget,
 then it might mean more billable hours.


-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Doug Steele
Sent: Thursday, July 03, 2008 10:19 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Article on stuff broken in Access 2007


I am being forced to work into Access 2007 by two of my clients.  One is a
branch of a large corporation which has switched completely to Office 2007
as company policy.  At the moment 'my' branch is running several Access 2000
BE/FE databases under Access 2007.  There have been minor issues, but no
significant problems.   We will convert over to full Access 2007 databases
gradually.  The other client is running a network with mixed Access
2003/Access 2007; the owner is a 'bleeding edge technology'  fan who is keen
to convert fully to 2007 and is also pressuring me to try using SQL Server
Express as the BE.  We have had some significant problems (like failed
updates and bizarre fatal errors) on the machines running Access 2007, but
unfortunately most problems have been intermittent and not reproducible on
my Access 2007 development system (running in a virtual machine).  FWIW, it
doesn't seem to matter whether the Access 2007 machines run the FE as an
Access 2003 .mdb or a converted Access 2007 .accdb.

Doug Steele

On Thu, Jul 3, 2008 at 8:06 AM, Charlotte Foust <cfoust at infostatsystems.com>
wrote:

> Does anyone in this list actually USE A2007?
>
> Charlotte Foust
>
>
--
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