Programming in Access Client/Server Solutions
Programming in Access client/server solutions is very similar to programming in Access database solutions. Most of the features of the Access object model when used in Access project files are the same as, or similar to, the features available when programming in Access database files.
The following additional methods of the DoCmd object have been added to open Access project views, stored procedures, and database diagrams: OpenView, OpenStoredProcedure, and OpenDiagram. Also, a number of the other methods of the DoCmd object have different behaviors and arguments to accommodate the differences in Access project objects. For information about these changes, search the Microsoft Access Visual Basic Reference Help index for "DoCmd object."
For information about working with Access objects, see Chapter 5, "Working with Office Applications." For information about working with Access reports, see Chapter 15, "Retrieving and Analyzing Data." For details on the differences in the functionality of Access methods, properties, and events between Access project files and Access databases, search the Microsoft Access Visual Basic Reference Help index for the method, property, and event names.
To work directly with the objects stored in a SQL Server database from an Access project, you should use ADO code. For an introduction to using ADO code, see Chapter 14, "Working with the Data Access Components of an Office Solution." For detailed information about using ADO code, see ADO Help. For information about using ADO to work with SQL Server 7.0, see the "Building SQL Server Applications" book in the SQL Server Books Online that is installed with SQL Server 7.0. The Microsoft Access Help also includes two components of SQL Server documentation: Transact-SQL Reference Help and SQL Server Error Messages. For information about using ADO and other data access object models to work with SQL Server 6.5 and 7.0, see the Hitchhiker's Guide to Visual Basic and SQL Server, Sixth Edition, by William R. Vaughn (Microsoft Press, 1998).