Jim Lawrence
accessd at shaw.ca
Fri Sep 16 10:26:37 CDT 2005
Hi Richard: It is not difficult to move the tables up to a SQL server using SQLs import tools 'Action/All tasks/Import'. That is the easy part. If the previous designer has made a botch of the tables you have normalize then from there. The next hurdle is moving or more accurately replacing the queries by migrating and re-building them in Stored Procedures. Next the big process. That is where you build a middle tier in your new version of access that connects to the SQL server. My recommendation is to use ADO-OLE but if time and money are issues much of the work can be done through an ODBC connection... but there are some inherent issues with this method; performance is one. This process is a big one and it will require a length of time. HTH Jim -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Griffiths, Richard Sent: Friday, September 16, 2005 4:34 AM To: AccessD Subject: [AccessD] A97 to SQL2000 Hi Group I have been given the task of moving A97 tables to SQL2000. The app was written by a user and so has little vba code (recordset processing etc). Is it as simple as importing data to SQL and setting up an ODBC DSN then reattaching the tables. I have tested on one or two tables and this appears to work okay. Are there known problems with this approach? Richard -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com