John W. Colby
jwcolby at colbyconsulting.com
Thu Aug 18 09:00:55 CDT 2005
Darren, If the BE is in Access and needs to be upgraded to SQL Server, try the upgrade wizard. I have run this on some fairly major Access Bes and it works pretty well. The only issue I had was dates which have different ranges between Access and SQL. The idea is to get the BE upgrading without any issues (data all moves without errors), then put the FE back in the BE and run it one more time. The wizard will place the data in SQL Server and create ODBC connections between the FE (no data anymore) and SQL Server. The ODBC connections look for all the world like normal links and at that point your FE should operate normally. At least the FE will work now. You can then start doing other things to make it faster, more robust etc. That's the "nutshell" version of the process. John W. Colby www.ColbyConsulting.com Contribute your unused CPU cycles to a good cause: http://folding.stanford.edu/ -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Darren Dick Sent: Thursday, August 18, 2005 8:46 AM To: Access Developers discussion and problem solving; Database Advisors Subject: [AccessD] A2000/3:Connecting to SQL Server Hello all New Job - Have to Learn SQL Server ASAP and MS Reporting Services. (Anyone know any good resources on MS Reporting Services?) Also I would like someone to hold my hand getting an ACCESS front end to talk with a SQL Server Backend. never done it - never had to - and I have no clue on how to do it. :-)) Anyone wanna hold my hand (No sweaty palms - I promise) or failing that some simple (and it really does have to be simple for me) tutorials? Many thanks Darren -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com