[AccessD] Access ADP file format

[Arthur Fuller]

I can see that viewpoint from the MS team. Maybe what I miss most was the
shock on the faces of snooty SQL Server guys who looked down their noses at
Access -- until I whipped up an app that addressed all the system tables
(admittedly with autoforms), and then loaded a stored procedure, made a
tiny change and saved it back to the SQL database. Elapsed time, maybe 5
minutes, tops. That wiped the condescending smiles off their faces.

On Fri, Mar 24, 2023 at 7:54 AM Jim Dettman via AccessD <
accessd at databaseadvisors.com> wrote:

> <<
> I know that at least one or two of you MVP types have insider access to
> these discussions. Care to shed some light on this particular decision?
> >>
>
>  Those discussions, if they occurred, would be under NDA.
>
>  But I can tell you that those types of marketing discussions are far
> beyond
> the purview of MVP's, and probably even many at Microsoft.
>
> << I recall asking another question similar to this, about why Access
> limits
> the number of relationship diagrams to 1.>>
>
>   I submitted a feature request a while back to be able to save more then
> one RI diagram (I think others did as well), but it never went anywhere.
>
> << The BE I'm working on currently has a half-dozen
> BEs, each corresponding to a group of tables within the overall domain.>>
>
>   So be careful with this.  While it's entirely workable for the most part,
> each BE you are opening takes additional overhead and resources.   I can't
> remember off-hand anyone recently having issues, and you should be fine
> with
> the half dozen or so, but I would not go much beyond that just to be safe.
>
> << I digress. Why did the Access team abandon the ADP file format?>>
>
>   My own personal opinion:   On the marketing front, Access has never been
> marketed as a development tool and was straying into Visual Studio waters.
> On the technical side (again at a guess), since it was a native interface
> into SQL, it would tightly couple each Access version to specific versions
> of SQL server, and there would be a constant need to match SQL server with
> each new version.
>
> Jim.
>
>
> -----Original Message-----
> From: AccessD On Behalf Of Arthur Fuller
> Sent: Friday, March 24, 2023 7:35 AM
> To: Access Developers discussion and problem solving
> <accessd at databaseadvisors.com>
> Subject: [AccessD] Access ADP file format
>
> Does anyone know why the Access team decided to kill that file format? I
> personally loved it. and wish it were still alive. Perhaps someone higher
> up on the food chain realized how good it was, and how bad it made SSMS
> look at the time, at threw a hissy fit.
>
> I know that at least one or two of you MVP types have insider access to
> these discussions. Care to shed some light on this particular decision?
>
> I recall asking another question similar to this, about why Access limits
> the number of relationship diagrams to 1. Turns out I can live with that: I
> have found an elegant work-around. Only recently did I realize that an
> Access FE can link to any number of BEs, so I have adopted the strategy of
> Schemas from SQL Server. The BE I'm working on currently has a half-dozen
> BEs, each corresponding to a group of tables within the overall domain.
> This works splendidly, and enables me to concentrate on a particular area
> of interest without having to wade through irrelevant clutter. I don't know
> about you, but when the database has ~100 tables, a single relationship
> diagram is incomprehensible.
>
> I digress. Why did the Access team abandon the ADP file format?
>
> --
> Arthur
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> https://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> https://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>


-- 
Arthur