A dickhead writes: "a a r o n _ k e m p f" <aaron_kempf@hotmail.com> wrote in message news:756f027d-deed-42b5-a626-bfb9a2152eb8@a21g2000prf.googlegroups.com... so grow a backbone, kid ADP have a future, for sure. Have you even seen what is coming in the next version? Have you heard about SQL Server Data Services? On Jul 22, 11:17 pm, "bcap" <b...@nospam.nowhere> wrote: Prior
Prior to Access 2007, everything I've done for about the last 5 years was done using ADP's. Certainly the technology has some horrendous bugs (which have been there since it's first incarnation and which, clearly, are never going to be fixed) but it's OK once you've found them all and found workarounds for them. Anyone who's never found any bugs when working with ADP's simply isn't trying
> First, for current development, is adp solid enough to use for complex projects; is development notably faster than with odbc and pass-through queries; are there performance gains? I haven't tried ADP with 2007, but I've never had any insurmountable problems with ADP, and the fact that all tables, views, functions, etc. show up instantly without any intervention on my part has been
In article <MPG.22e55a0a8910a639896ef@msnews.microsoft.com>, amos@amos2.com says... I'd be interested to hear from some of you that are using adps, or have tried thoroughly and given up on them. I currently use pass-through queries and stored procedures with Access 2003 mdbs to sql server 2005. That works pretty ok once you get the hang of it all. I've always regarded projects
I'd be interested to hear from some of you that are using adps, or have tried thoroughly and given up on them. I currently use pass-through queries and stored procedures with Access 2003 mdbs to sql server 2005. That works pretty ok once you get the hang of it all. I've always regarded projects as being off the table since MS clearly shifted away from adp years ago. I suppose there are
