[AccessD] A2K3 ADP

If this is accurate, I can live with it. Why? Because the replacement for
Enterprise Manager + Query Manager etc. is so slick that my old argument
that ADP was the single best interface into SQL is now as obsolete as EM.
Incidentally, even if you decide to keep all your SQL databases in 2000
format, install the 2005 baby asap. It is a new dawn, a new day for SQL
development and management.
While obviously there are numerous features available only in 2005, the fact
that it can maintain 2000 databases makes this transition a lot less
painful.
All that said, JC has a point. VS.NET 2005 is a splendid piece of work.
A.

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of MartyConnelly
Sent: November 18, 2005 1:46 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] A2K3 ADP


I don't know whether this statement from Mary Chipman still hold's true
It is a year old regarding SQL Express 2005 and Access ADP's.
 From one of the microsoft non-google searchable newsgroups.
I think they are still messing around with the EM for SQL 2005


"You will not be able to use any of the designers with SQLS 2005
databases, whether it's SQL Express or the Developer edition. IOW, you
won't be able to create databases, tables, views or any other database
objects from an ADP. The only support that is envisioned is that you
will be able to connect an Access front-end to a SQLS 2005 back end if
it is running in SQLS 2000 compatibility mode, so your forms, reports
and other local Access objects should still run. There is no service
pack or quick fix being planned as far as I know because of the amount
of work it would entail. If you stop to think about it, it's pretty
hard to see how accomodating new Yukon features like CLR assemblies
and complex data types in the ADP designers could be achieved without
a complete rewrite. "

Steve Erbach wrote:

>Robert,
>
>I'm not concerned about coding something like this. I'm more interested in
>the state of Microsoft development and support. I have a Universal MSDN
>subscription, but I confess I don't pay that much attention to what's
>happening with Access. It just seemed to me that ADP's were so handy.
>
>Steve Erbach
>Neenah, WI
>
>
>On 11/18/05, Robert L. Stewart <rl_stewart at highstream.net> wrote:
>  
>
>>Not really, since Microsoft is not going to continue support of
>>ADPs. All those using them will have to re-tool their applications.
>>
>>I have some massive MDBs that connect only to SLQ Server, using
>>ODBC. I was going to rewrite them to ADPs, but when I heard they
>>were not going to be supported, I stopped. I am rewriting them in
>>.Net instead.
>>
>>And, stored procs work fine using ODBC, just use a pass through
>>query. Normally, I have one without the parameters (_0) that I use
>>to build the one with the parameters (_1). And I simply change the
>>SQL statement in code for the _1 query. If you are worried about the
>>connection string, simply replace it through code also.
>>
>>Robert
>>
>>At 10:11 AM 11/18/2005, you wrote:
>>    
>>
>>>Date: Fri, 18 Nov 2005 10:54:16 -0500
>>>From: "William Hindman" <wdhindman at bellsouth.net>
>>>Subject: Re: [AccessD] A2K3 ADP
>>>To: "Access Developers discussion and problem solving"
>>><accessd at databaseadvisors.com>
>>>Message-ID: <001901c5ec58$54a7fde0$6101a8c0 at JISREGISTRATION.local>
>>>Content-Type: text/plain; format=flowed; charset="iso-8859-1";
>>>reply-type=original
>>>
>>>...just call me Dinosaurus Rex :)
>>>
>>>Willam
>>>      
>>>

-- 
Marty Connelly
Victoria, B.C.
Canada



-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com