Apologies if this has been discussed before… but think I’m at a crossroads… maybe as other access developers have been over the past year or 2…. What route do we take ?
Been designing and building db apps for over 20 years, for the past 12 years been running my own development business, am now contracting and being asked to come up with a future strategy for current client.My preference for many, many years has been using ADP projects and SQL back ends using ADO, and now thinking that maybe I’ve got to change…. (un-willingly I might add !!!) As a lightweight RAD tool I really can’t think of anything I could have used over the years that would’ve given me and my clients the flexibility that we’ve had. For years I’ve used access as an exceptional front end development product to SQL Server. So…. Where do we go…. I can’t find anything that ‘officially’ states ADP’s will be no more, but ‘rumour’ seems to be pointing this way….. the internet consensus seems to be .accdb and ODBC linked tables using DAO…. Not sure, is this a step back ? discussion point maybe
(.....probably should make clear.... I use stored procedures for everything !!! select,insert, update, delete, everything data related is via stored procedures, so in my eyes using the ADP/ADE for what it was possibly intended for, everything unbound, leightweight, a fantastic RAD development tool for SQL server..... was specifically asked by a client years ago to execute all data manipulation via SP's, since then have always developed that way..... )
Client’s moving to sharepoint, so I can see all them corporate ‘user’ created desktop data solutions will probably end up in sharepoint if no processing/complicated sturcture is required, (we’re talking 1000’s) whether this be via Access Services or sharepoint designer is yet to be seen (or even lightswitch apps could be a possibility outside sharepoint). But what about the larger desktop/team/ business apps that require a lot more processing & coding, that have larger relational models, more business critical, where the full benefits of the back end are required…. What direction do we take or advise from a desktop product/RAD strategy without going .NET route….
Personally… SQL backends with sharepoint consumed ‘intranet/internet’ interfaces and ADP interfaces would be perfect !!!! What’s peoples thought’s ? (thanks for taking the time to read & reply)
Been designing and building db apps for over 20 years, for the past 12 years been running my own development business, am now contracting and being asked to come up with a future strategy for current client.My preference for many, many years has been using ADP projects and SQL back ends using ADO, and now thinking that maybe I’ve got to change…. (un-willingly I might add !!!) As a lightweight RAD tool I really can’t think of anything I could have used over the years that would’ve given me and my clients the flexibility that we’ve had. For years I’ve used access as an exceptional front end development product to SQL Server. So…. Where do we go…. I can’t find anything that ‘officially’ states ADP’s will be no more, but ‘rumour’ seems to be pointing this way….. the internet consensus seems to be .accdb and ODBC linked tables using DAO…. Not sure, is this a step back ? discussion point maybe
(.....probably should make clear.... I use stored procedures for everything !!! select,insert, update, delete, everything data related is via stored procedures, so in my eyes using the ADP/ADE for what it was possibly intended for, everything unbound, leightweight, a fantastic RAD development tool for SQL server..... was specifically asked by a client years ago to execute all data manipulation via SP's, since then have always developed that way..... )
Client’s moving to sharepoint, so I can see all them corporate ‘user’ created desktop data solutions will probably end up in sharepoint if no processing/complicated sturcture is required, (we’re talking 1000’s) whether this be via Access Services or sharepoint designer is yet to be seen (or even lightswitch apps could be a possibility outside sharepoint). But what about the larger desktop/team/ business apps that require a lot more processing & coding, that have larger relational models, more business critical, where the full benefits of the back end are required…. What direction do we take or advise from a desktop product/RAD strategy without going .NET route….
Personally… SQL backends with sharepoint consumed ‘intranet/internet’ interfaces and ADP interfaces would be perfect !!!! What’s peoples thought’s ? (thanks for taking the time to read & reply)
Last edited: