Jim Hewson
jm.hwsn at gmail.com
Wed Dec 12 13:05:28 CST 2012
Thank you, that's what I needed to know. Jim On Wed, Dec 12, 2012 at 1:00 PM, Jim Dettman <jimdettman at verizon.net> wrote: > Jim, > > Make sure they run the 32 bit version of Office. > > Starting with 2010, Access is a bit picky about syntax and what not, so > you might have some remedial work to do, but nothing should give you a > major > headache. Make sure the app is error free as it stands now and check right > after conversion as well. > > Also, MSCAL.OCX (calendar control) is no longer included. You'll need to > switch to the native date/time picker or use a 3rd party control. > > Outside of that, 2007 to 2013 or running the 2007 DB in 2013 should give > little trouble. > > Jim. > > -----Original Message----- > From: accessd-bounces at databaseadvisors.com > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Jim Hewson > Sent: Wednesday, December 12, 2012 01:09 PM > To: Access Developers discussion and problem solving > Subject: [AccessD] Access 2007 compatibility with Access 2013 > > I created a database for a non-profit organization that has been running > for about 4 years with no problems. > It was written in Access 2007. They will be "upgrading" to Office 2013 in > the very near future. > Will there be any compatibility issues that I need to know about? > Thanks, > Jim > -- > 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 >