If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#11
|
|||
|
|||
accdb vs adp
developing ADP on the desktop, and then upsizing it to the server is
the preferred method On Feb 19, 7:14*pm, "Larry Linson" wrote: "David W. Fenton" wrote in messagenews:Xns9D2486117BC84f99a49ed1d0c49c5bbb2@7 4.209.136.82... =?Utf-8?B?YnJpYW5r?= wrote in : I have inherited an A2007 adb with a connection to SS2K5. *I have recently begun trying to follow the various VBA code compiled by four different consultants which is a bit of a challenge in itself. *Since my company's needs have changed over the past months I feel that it would be cost effective to simply create a new db from scratch. *However, I am not sure of the advantages of ADPor simply sticking with ACCDB. *I would appreciate feedback on this scenario. For what it's worth, Microsoft has been deprecating ADPs in favor of MDB/ODBC for the last several years. This is likely to change with the next version of Access (i.e., the version *after* 2010) because the Access team has been doing a special project in trying to seek out users of SQL Server and make Access work better with it. So, I'd expect ADPs to get new life in Access 15 (ADPs have been basically ignored in A2007 and A2010, which should tell you something about how well-implemented they were). ODBC really is old and creaky, and I really wish ODBC2 would be created and incorporate the best aspects of ADO. That wouldn't be .NET-compliant, but it would cover a whole host of issues that come with using ODBC access to modern databases. For now, I would not contemplate using anADPfor any purpose. If the Access team does as stellar a job on improving ADPs as they have with the A2010 Sharepoint integration, it should be a big hit, and then become the de facto best choice for development against SQL Server back ends. The main flaw for me with that, though, is that it's not back-end agnostic, which is something I consider important. I'd love to have the capabilities of anADPwhen connecting to MySQL, for instance. But that would be MS giving up a certain amount of proprietary advantage. On the other hand, MS has done that with real browser agnosticism with Sharepoint 2010, so it's possible. But I wouldn't hold my breath on that one! There may be something "like" anADP, but ADPs rely on OLEdb and the current access mechanisms in "real development" (the bigots name for Dot Net stuff) use something other than OLEdb. I've worked in very few shops where they had a server back end, in which the DBA would allow "mere developers" to do design-side work on "the DBA's server". Yes, they had a very proprietary attitude. No, it wasn't likely to change. With small clients, you probably won't face that problem... I suspect that the fact that Microsoft targets enterprise customers may have something to do with their "neglect" of ADPs... they found out that many of the wonderful features they had included were simply prohibited to developers in their target audience. *Larry Linson *Microsoft Office Access MVP |
#12
|
|||
|
|||
accdb vs adp
David;
Just because you're not using the worlds most popular database (SQL Server) doesn't mean it's in anyone's best interests to use an obsolete database -Aaron On Feb 19, 10:10*am, "David W. Fenton" wrote: =?Utf-8?B?YnJpYW5r?= wrote : I have inherited an A2007 adb with a connection to SS2K5. *I have recently begun trying to follow the various VBA code compiled by four different consultants which is a bit of a challenge in itself. *Since my company's needs have changed over the past months I feel that it would be cost effective to simply create a new db from scratch. *However, I am not sure of the advantages of ADPor simply sticking with ACCDB. *I would appreciate feedback on this scenario. For what it's worth, Microsoft has been deprecating ADPs in favor of MDB/ODBC for the last several years. This is likely to change with the next version of Access (i.e., the version *after* 2010) because the Access team has been doing a special project in trying to seek out users of SQL Server and make Access work better with it. So, I'd expect ADPs to get new life in Access 15 (ADPs have been basically ignored in A2007 and A2010, which should tell you something about how well-implemented they were). ODBC really is old and creaky, and I really wish ODBC2 would be created and incorporate the best aspects of ADO. That wouldn't be .NET-compliant, but it would cover a whole host of issues that come with using ODBC access to modern databases. For now, I would not contemplate using anADPfor any purpose. If the Access team does as stellar a job on improving ADPs as they have with the A2010 Sharepoint integration, it should be a big hit, and then become the de facto best choice for development against SQL Server back ends. The main flaw for me with that, though, is that it's not back-end agnostic, which is something I consider important. I'd love to have the capabilities of anADPwhen connecting to MySQL, for instance. But that would be MS giving up a certain amount of proprietary advantage. On the other hand, MS has done that with real browser agnosticism with Sharepoint 2010, so it's possible. But I wouldn't hold my breath on that one! -- David W. Fenton * * * * * * * * *http://www.dfenton.com/ usenet at dfenton dot com * *http://www.dfenton.com/DFA/ |
#13
|
|||
|
|||
accdb vs adp
ADP is the best answer.
Do you really think that it's efficient to manually copy queries in and out of every front end every time you open the DB? keep your data, your logic, and your queries in one place- where they belong. SQL Server and ADP. -Aaron On Feb 18, 8:55*am, briank wrote: Thank you for your thoughts on this situation. *Currently my employee seems to be firmly in place with using SQL 2005. *With this in mind I am now trying to determine which is best with the SQL connection, either accdb oradp. I hear opinions supporting each way but I'm trying to determine what factual evidence is the most swaying. *I appreciate any thoughts on this. "GBA" wrote: I seem to be in a minority in believing that the ever increasing power of the PC, plus that LANs generally are not bandwidth constrained - means that the requirement to move to sqlserver is pushed further and further away each year. There seems to be an overwhelming fixed opinion that if any Access problem exists it is viewed that the solution is to 'up size it' to sqlserver..... * Which is to say the opinion is to move to sqlserver and not move away from sqlserver as most presume growth. There are several good & valid reasons to move to sqlserver - it is a very solid product - - so at the same time there would need to be solid reasons to move away from it. *If your organization is running sqlserver routinely for several other db apps then one would tend to think you should stay with it. On the otherhand you kind of imply your company is downsizing in various dimensions - and going strictly PC/LAN environment is certainly more frugal than managing sqlserver. *Fundamentally can Access do the job? *that's kind of yes/no...and then which is less/more painful? *managing the exiting environment vs the effort to downsize it off sqlserver.... Am not sure any generic advice can really assess your situation from a forum... "briank" wrote: I have inherited an A2007 adb with a connection to SS2K5. *I have recently begun trying to follow the various VBA code compiled by four different consultants which is a bit of a challenge in itself. *Since my company's needs have changed over the past months I feel that it would be cost effective to simply create a new db from scratch. *However, I am not sure of the advantages ofADPor simply sticking with ACCDB. *I would appreciate feedback on this scenario. *TY. |
#14
|
|||
|
|||
accdb vs adp
ADP means you never have to deal with corruption or performance
problems On Feb 18, 6:28*am, briank wrote: I have inherited an A2007 adb with a connection to SS2K5. *I have recently begun trying to follow the various VBA code compiled by four different consultants which is a bit of a challenge in itself. *Since my company's needs have changed over the past months I feel that it would be cost effective to simply create a new db from scratch. *However, I am not sure of the advantages ofADPor simply sticking with ACCDB. *I would appreciate feedback on this scenario. *TY. |
#15
|
|||
|
|||
accdb vs adp
Can ACCDB work over wireless?
I dont' think so! On Feb 18, 6:28*am, briank wrote: I have inherited an A2007 adb with a connection to SS2K5. *I have recently begun trying to follow the various VBA code compiled by four different consultants which is a bit of a challenge in itself. *Since my company's needs have changed over the past months I feel that it would be cost effective to simply create a new db from scratch. *However, I am not sure of the advantages ofADPor simply sticking with ACCDB. *I would appreciate feedback on this scenario. *TY. |
#16
|
|||
|
|||
accdb vs adp
"a a r o n . k e m p f @ g m a i l . c o m" wrote in
message ... Just because you're not using the worlds most popular database (SQL Server) At last count, Access/JET had more users than all other databases combined. While SQL-Server is definitely a great choice in many cases, your statement is factually incorrect (as usual) -- Arvin Meyer, MCP, MVP http://www.datastrat.com http://www.mvps.org/access http://www.accessmvp.com |
#17
|
|||
|
|||
accdb vs adp
"David W. Fenton" wrote:
But all of this will change 2-3 years from now, with the release of Access 15, which apparently is going to address the neglect of ADPs in the last two releases. That isn't enough to convince me that it's wise to trash an MDB app and replace it with an ADP even then, but it's worth keeping in mind (i.e., the investment in moving to ADP could pay off 2 or 3 years down the road; on the other hand, the Access 15 ADPs could be sufficiently different to make current ADPs problematic). I hadn't heard this. Any URLs? Tony -- Tony Toews, Microsoft Access MVP Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/ For a convenient utility to keep your users FEs and other files updated see http://www.autofeupdater.com/ Granite Fleet Manager http://www.granitefleet.com/ |
#18
|
|||
|
|||
accdb vs adp
"a a r o n . k e m p f @ g m a i l . c o m"
wrote: ADP is the best answer. In a few scenarios sure. Do you really think that it's efficient to manually copy queries in and out of every front end every time you open the DB? I don't see how this works. Tony -- Tony Toews, Microsoft Access MVP Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/ For a convenient utility to keep your users FEs and other files updated see http://www.autofeupdater.com/ Granite Fleet Manager http://www.granitefleet.com/ |
#19
|
|||
|
|||
accdb vs adp
"a a r o n . k e m p f @ g m a i l . c o m" wrote in message ... Can ACCDB work over wireless? I dont' think so! Yes it does. We have a new off line mode, and if the connection breaks, you can continue using the local data store. When the connection is restored...data again beings to sync. This feature was added to the new ACE for use with disconnected SharePoint tables. So, we talking about cached disconnected data. And, over an intermitting connection that is constantly breaking and re-connecting and disconnecting the application will continue to run. Data is syncing much like a email send/receive type of model. You don't get this ability with ADP, but you sure do with ACCDB over wireless when using SharePoint as your data store. This ability is a result of changes made to ACE (the new JET) engine. Users of ADP can only dream about such functionally here. It is possbile you not heard of this new thing called the internet. With a future world of Smartphone's, Wi-Fi hotspots then it is a no brain that we need technology that can work in these environments. This is clearly one big future of our industry. Access has joined this new party, but this feature is not available by using ADP's. It is with accDB -- Albert D. Kallal (Access MVP) Edmonton, Alberta Canada |
#20
|
|||
|
|||
accdb vs adp
"Tony Toews [MVP]" wrote in message
... "David W. Fenton" wrote: But all of this will change 2-3 years from now, with the release of Access 15, which apparently is going to address the neglect of ADPs in the last two releases. That isn't enough to convince me that it's wise to trash an MDB app and replace it with an ADP even then, but it's worth keeping in mind (i.e., the investment in moving to ADP could pay off 2 or 3 years down the road; on the other hand, the Access 15 ADPs could be sufficiently different to make current ADPs problematic). I hadn't heard this. Any URLs? Tony -- Neither have I, and I just came back from the summit with some intense vision sessions on access 15... -- Albert D. Kallal (Access MVP) Edmonton, Alberta Canada |
Thread Tools | |
Display Modes | |
|
|