[AccessD] Access 2016 now with BigInt

[David McAfee]

I liked ADPs because all the tables and queries (actually views and stored
procedures) were in SQL and Access was for forms and reports.

Yes, I can connect to SQL from an mdb or accdb, but it was so much simpler
via an adp, especially with stuff like cascading combo boxes and list boxes.

No need to first modify a query def before calling a pass through query.

I think I was one of the few people that used them and liked them.

There were many other reasons, but no used crying over that spilled milk.

and I still dislike the A2007 + interface. <2003 was so much better IMO.

D





On Tue, Mar 7, 2017 at 6:37 AM, Dan Waters <df.waters at outlook.com> wrote:

> Hi David,
>
> Several years ago I had a request from a customer to look into modifying
> their Access system to work across a WAN.  Obviously and ADP was a choice.
> However, I realized that connecting to a SQL Server database using SQL
> Command language in code was exactly the same work in an MDB as in an ADP.
> From what I could tell, and ADP was just an MDB with some features
> missing.  For example an ADP would not allow you to add a local table for
> temp data storage.  I had to conclude that ADP's were somehow just a
> marketing mechanism to show that Access could be used on a WAN.  My
> customer decided to use a Citrix server instead so I never did get to
> rewrite that system.
>
> So if you want to connect to a SQL Server database across a WAN you can
> still do that!
>
> Good Luck!
> Dan
>
> PS - Get a copy of the book 'Microsoft Access Developer's Guide to SQL
> Server.
>
> -----Original Message-----
> From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of
> David McAfee
> Sent: Monday, March 06, 2017 22:25
> To: Access Developers discussion and problem solving
> Subject: Re: [AccessD] Access 2016 now with BigInt
>
> right?
>
> But still...
>
> Loss of ADP connectivity
>
> Stupid ribbon
>
> Stupid interface (vs A2003 and earlier)
>
> Still havent fixed old bugs from Access 95/97 such as Send Keys causing
> weird behavior...
>
> On Mon, Mar 6, 2017 at 6:48 PM, Mark Simms <marksimms at verizon.net> wrote:
>
> > First major enhancement in 5 years.....LOL.
> >
> >
> > > -----Original Message-----
> > > From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On
> > > Behalf Of Gustav Brock
> > > Sent: Monday, March 06, 2017 1:53 PM
> > > To: Access Developers discussion and problem solving
> > > Subject: [AccessD] Access 2016 now with BigInt
> > >
> > > Hi all
> > >
> > > Should you need to handle BigInt natively with Access:
> > >
> > > https://blogs.office.com/2017/03/06/new-in-access-2016-large-number-
> > > bigint-support/
> > >
> > > In Access, BigInt is labelled Large Number.
> > >
> > > /gustav
> > > --
> > > 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
> >
> --
> 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
>