jwcolby
jwcolby at colbyconsulting.com
Mon Mar 2 09:56:56 CST 2009
I was under the impression that it no longer worked with SQL Server 2005. John W. Colby www.ColbyConsulting.com Arthur Fuller wrote: > Well our group is at least two, David. I was one of the earliest adopters of > ADP and the app had 250+ tables and tons of sprocs and UDFs and 75+ users > connected to a TS box, and it worked very well. I hope the MS people don't > decide to kill this approach because it works extremely well and at a > fraction of the cost of the equivalent .NET solution. (Don't get me wrong, I > like .NET too and also Ruby on Rails.) > > Arthur > > On Fri, Feb 27, 2009 at 2:27 PM, David McAfee <davidmcafee at gmail.com> wrote: > >> Yes, its definitely planned. :( >> >> I prefer ADPs to MDBs, not only for the ability to change the >> connection to the BE so easily, but also the ease of assigning a store >> procedure to the row source of a listbox. >> >> me.lstMyListBox.rowsource = Exec stpSomeStoredProcedure " & >> intSomeIntAsMyInputParameter >> >> I never liked using temp tables in my MDBs because of bloat issues. >> >> You can handle temp tables in two ways: >> 1. Upon opening a form, create a ##tempTable in SQL via a stored >> procedure, be sure to drop it on FormClose >> 2. Another choice is to create a temp db on the user's PC, use >> preferred method to communicate with that mdb, discard when finished. >> >> I have used both, and both methods work well. >> >> I know I'm one of the very few that likes/still uses ADPs. >> >> David >> >> On Fri, Feb 20, 2009 at 12:16 PM, <rusty.hammond at cpiqpc.com> wrote: >>> Thanks for the reply. Since the SQL server is 2005 I have to use SQL >> Server >>> Management Studio anyway. >>> >>> >From the search you used it sounds like most people prefer to go with >> the >>> mdb and with the release of SQL 2008, an Access 2007 adp can't make >> changes >>> to the SQL objects either so you really can't count on being able to use >>> that feature consistently as time goes on. >>> >>> I really like the ability to change the connection from a test back end >> to >>> production very easily from an adp, but there's code out there to work >>> around that issue in an mdb. Seems like the advantages of an adp are >> going >>> away. You think that's planned? >>> >>> >>> Thanks, >>> >>> Rusty >>> >>> -----Original Message----- >>> From: accessd-bounces at databaseadvisors.com >>> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Dan Waters >>> Sent: Friday, February 20, 2009 10:58 AM >>> To: 'Access Developers discussion and problem solving' >>> Subject: Re: [AccessD] Should I use an adp or an mdb >>> >>> Use an mdb! The primary goal of using an adp was that it gave you the >>> ability to manage objects in the SQL Server database you are using from >>> within Access - an mdb can't do that. >>> >>> But, since SQL Server 2005 Express (free) was released, you can easily >>> manage those objects with SQL Server Express Management Studio (also >> free). >>> This wasn't easily possible with MSDE. >>> >>> So, by using an Access mdb and SQL Server Express Management Studio you >> can >>> get all the benefits of both. >>> >>> With an mdb, you can use either table links for use on a LAN, or you can >>> connect using OLEDB (like an adp would) for use on a WAN. Also in an >> mdb, >>> you can have temp tables in the FE. >>> >>> I did a search on 'Access mdb vs adp' and got many good sites. >>> >>> Dan >>> >>> -----Original Message----- >>> From: accessd-bounces at databaseadvisors.com >>> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of >>> rusty.hammond at cpiqpc.com >>> Sent: Friday, February 20, 2009 10:34 AM >>> To: accessd at databaseadvisors.com >>> Subject: [AccessD] Should I use an adp or an mdb >>> >>> I'm getting ready to create a new application with a SQL server backend. >>> I'm familiar enough with using SQL server but my question is, do I use an >>> Access Data Project or a regular mdb with links to the tables as a front >>> end. >>> >>> I've used both and would like to use the adp but I've heard rumblings >> that >>> they will be going away and don't want to rewrite this app in the near >>> future. I'm currently using Access 2003. >>> >>> Any suggestions? >>> >>> Rusty Hammond >>> IT Dept. - B-20 >>> CPI Qualified Plan Consultants, Inc. >>> (620) 793-8473 ext. 416 >>> rusty.hammond at cpiqpc.com >>> >>> >>> ********************************************************************** >>> WARNING: All e-mail sent to and from this address will be received, >> scanned >>> or otherwise recorded by the CPI Qualified Plan Consultants, Inc. >>> corporate e-mail system and is subject to archival, monitoring or review >> by, >>> and/or disclosure to, someone other than the recipient. >>> ********************************************************************** >>> -- >>> AccessD mailing list >>> AccessD at databaseadvisors.com >>> http://databaseadvisors.com/mailman/listinfo/accessd >>> Website: http://www.databaseadvisors.com >>> >>> >>> -- >>> AccessD mailing list >>> AccessD at databaseadvisors.com >>> http://databaseadvisors.com/mailman/listinfo/accessd >>> Website: http://www.databaseadvisors.com >>> >>> ********************************************************************** >>> WARNING: All e-mail sent to and from this address will be received, >>> scanned or otherwise recorded by the CPI Qualified Plan Consultants, Inc. >>> corporate e-mail system and is subject to archival, monitoring or review >>> by, and/or disclosure to, someone other than the recipient. >>> ********************************************************************** >>> -- >>> AccessD mailing list >>> AccessD at databaseadvisors.com >>> http://databaseadvisors.com/mailman/listinfo/accessd >>> Website: http://www.databaseadvisors.com >>> >> -- >> AccessD mailing list >> AccessD at databaseadvisors.com >> http://databaseadvisors.com/mailman/listinfo/accessd >> Website: http://www.databaseadvisors.com >>