Jim Lawrence
accessd at shaw.ca
Mon Jan 10 14:15:35 CST 2011
Thanks for the info... The data importation is the key point and I have been playing around with and eventually ended with Microsoft's SQL Server Migration Assistant (SSMA) for Access (http://tinyurl.com/37ltooy) to that end. It may be simple once it is configured properly but as of yet it is only sort of working(?) I have dragged all the queries and tables into a single MDB (no minor feat as it required the merging two applications) and am hoping this time it will push/translate the objects through without a hiccup... (May have to migrate the master MDB from 2003 to 2007 to make it all work) This exercise was supposed to be quick and dirty. If can think of any better solution don't hesitate to enlighten me, ;-) After all this fun I am sure the client's site will be much easier to configure...? Yeah...right... Jim -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Stuart McLachlan Sent: Sunday, January 09, 2011 2:39 PM To: Access Developers discussion and problem solving Subject: Re: [AccessD] Upsizing I would just import all of the BE tables into SQL Server and then relink the FE using ODBC. I've got a couple of systems where I do something similar. The FE application can work with either an Access or a SQL Server BE depending on the environment. It's simply a matter of running some re-linking code to switch between BEs. -- Stuart On 9 Jan 2011 at 13:53, Jim Lawrence wrote: > Hi All: > > I know that Upsizing has been discussed at certain points but I now > have to do a quick and dirty upgrade before I can seriously translate > a site to ADO-OLE. > > Right now the client has an Access2003 application sitting on a > Windows Server 2003 or 2008 (not sure yet). There is a SQL Server 2005 > on the computer. Due to some bizarre unstable connection issues we > have to move things up and quickly. > > The current application is broken into FE and BE. > > 1. Should the FE and BE be merged before running the upsizing or not? > 2. Will all the queries and reports have to be manually updated? 3. Is > there anyway to modify the Upsize generated SQL connections to point > to another SQL server? 4. Is there a better way to do this process > than using the Upsize wizard? 5. Is there any other issues that should > be handled or looked out for? > > TIA > 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