Arthur Fuller
artful at rogers.com
Fri Mar 7 07:21:00 CST 2003
I don't see the point of this approach. In fact I think it would complicate your problem rather than simplifying it, since you'd get all the problems and none of the benefits. Instead I suggest: A) make a copy of both the FE and BE. B) import the BE into the copied FE. C) find all record and row sources that begin with the word SELECT and change them to saved queries. D) run the upsizing wizard on this new combined FE-BE. You will end up with an MSDE database and an ADP FE that directly points to the database rather than going through ODBC. Now you can enjoy the benefits: speed, direct access to stored procedures, UDFs and views. HTH, Arthur -----Original Message----- From: accessd-admin at databaseadvisors.com [mailto:accessd-admin at databaseadvisors.com] On Behalf Of Eric Goetz Sent: March 6, 2003 8:26 PM To: AccessD at databaseadvisors.com Subject: [AccessD] AXP mde fe / be to fe / MSDE Hi, I'm looking to get my feet wet in MS SQL Server. I've got an Access XP mde fe/be using A2K file format that is used for sales reports. There are three users; one all the time, the others occasionally. There is talk of creating a web front end for the 45 remote sales people. This seemed to me to be a potential project for getting some experience with the MSDE. That would leave me ready to move to SQL Server. To get a simple start, I thought I would just replace the back end with MSDE and link with ODBE. How does this work out in practice - especially from a deployment and development standpoint? Has anyone tried this? If I got this going, I thought I could try some pass through queries. Is this a good way to start with SQL Server? Thanks, Eric _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com