newsgrps
newsgrps at dalyn.co.nz
Sun Jun 12 15:45:03 CDT 2011
John, I am not sure if there is an automatic conversion tool but you can create a new ADP and import your forms, reports, macros, modules into it. Queries will not import because ADP's show the SQL views and stored procedures. Tables also all come from SQL (no local Access tables). When an ADP is opened in Access there is a Connection item in the File Menu. This is used for setting up the connections to an SQL database. All record sources for forms, reports, combos etc will need to be written as stored procedures, views or tables - no local queries. New form properties for Unique Table, Resync Command, and Input Parameters are used to make sure the correct data is retrieved. Books I found helpful (they are pretty old now but are still relevant) were: SQL: Access to SQL Server (Harkins and Reid) Microsoft Access Developers Guide to SQL Server (Chipman and Baron) Access 2002 Enterprise Developers Handbook (Litwin, Getz and Gunderloy) Regards David Emerson Dalyn Software Ltd New Zealand At 13/06/2011, jwcolby wrote: >I am about to play around with my first ADP. I know nothing, have >never done one. > >I have a smallish but well developed Access FE already working with >existing data in SQL Server. I use ADODB linked tables with the SQL >Server IP:Port, Username and password hard coded (saved) in the >tables, and DAO code for many purposes. > >So what do I need to know to convert my MDB based linked FE to an >ADP solution? Also what do I do when I move my data from one SQL >Server instance to another (I will be doing that soon). The IP part >of the server info will change when I do that. > >Any words of wisdom before I begin? > >-- >John W. Colby >www.ColbyConsulting.com >-- >AccessD mailing list >AccessD at databaseadvisors.com >http://databaseadvisors.com/mailman/listinfo/accessd >Website: http://www.databaseadvisors.com