Jim Dettman
jimdettman at verizon.net
Thu May 22 06:03:35 CDT 2014
Use 2010 and if you can, 2013. Although be careful with 2013. Many client DB features were removed. A2010 is the last full featured version of Access for client(desktop) DB's. There was a bug in JET/ACE in relation to multi-core processors running under 64 bit OS's. Not sure when it was fixed. Microsoft was pretty mum about it (it's never been documented to my knowledge). 2010 should certainly have the fix, but A2007 may not. It was discovered when Windows Server 2008 R2 was released. Jim. -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Brad Marks Sent: Wednesday, May 21, 2014 10:55 PM To: Access Developers discussion and problem solving Subject: [AccessD] Access 2007 Runtime on Windows Server 2012 R2 All, We have a small Access 2007 "Runtime" application that runs under Windows Small Business Server 2003. This scheduled application runs every night in an unattended mode. It pulls data from a SQL Server database and generates several reports (PDF) that are automatically e-mailed to select employees. We are now migrating to new server hardware which will be running Windows Server 2012 R2. Will an Access 2007 (Runtime) application work properly under Windows Server 2012 R2? Would it be better to use Access 2010 Runtime? Thanks, Brad -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com