Join the Conversation

3 Comments

  1. Aaaron, How do like the thought of Access 2013 with no support for ADP? Going back to linked tables is a nightmare.

    1. Oh, I won’t use linked tables.. no matter what. I’m so entrenched in SQL, most of my time is with SQL Server Analysis Services, Reporting Services anyways.. And I’ll just keep using 2010 until they pry it from my hands. I really only use it for a little bit of data entry, a little bit of testing/forms.. I really really to this day just LOVE forms in ADP, I think that they’re the best platform for data entry anywhere.

      And of course, I use it to test / browse views/tables (right-click sort, filter, I can’t dev/test/deliver without that functionality)…

      I generally prototype in ADP, and then transfer the ETL-type logic to VB.net console apps.. that’s the model I’ve been following most of the past 5 years or so.

      I am quite interested in the new ‘Web Database’ thing.. I haven’t been able to try it with the RTM copy of SharePoint 2013.. but supposedly, just uploading an Access database is supposed to automatically upsize the app to a DEDICATED SQL Server, instead of a couple of layers on top of sharepoint, it’s more direct SQL, from what I understand.

      I just don’t know if it’s worth the effort.. I’ll know in about another week, it’s hard, SQLPASS this week 🙂

      I’m probably more fascinated with Visual Studio Lightswitch at this point, and gosh.. it supports other database engines..

      After the way that Microsoft killed Office Web Components and the ADP, I’d rather move away from SQL Server entirely.. but Lightswitch intrigues me.
      I just finally got the new TFS express up at work, with SSRS and SSIS in there.. (haven’t done SSAS, most of my SSAS is still SQL 2000 upsized to 2008, so it’s hard to source-control)

      And I got lightswitch with TFS working.. Now I just need to watch some more youtube vids on Ligthswitch.. the whole ‘platform independence’ I really like.. how you can use SharePoint as a backend OR SQL Server, I think that you can also use Oracle and mySQL..

      I just haven’t been able to really understand ASP.net.. I truly think that it’s overkill for what I want to do.

      So I still do some stuff in Classic ASP (of all things LOL).

      Just this past couple of weeks, I’ve been deploying this old Office Web Components website from 6-7 years ago.. I think that it’s some of the coolest stuff I’ve ever written… Just simple Ad-Hoc reporting, drag and drop pivot tables, with centralization.

      I just despise MS Excel.. I despise giving people data dumps in MS Excel, I hate people doing reporting in Excel.. I don’t really get it.. where Microsoft is leading us.

      I see Access as a dead end entirely, I just can’t handle linked tables.. Maybe they’ll have a resurgence, now that ODBC is the future LOL.. I just still think that the idea of using a DSN is ridiculous, I want to maintain ONE link to SQL Server that’s easy to change everywhere.

      Specifically, it’s the connection strings on the SQL-passthrough queries that drives me crazy more than anything else. I shouldn’t have to write a loop for that.

      Did you see my link the other day about VSTO and MS Access? I -MIGHT- just start playing around with VSTO and and MS Access 2007 / 2010, just to see what I can do.

  2. Confirmed, Access 2003 SP1, Access 2007 SP2 and Access 2010 (ADP/MDB/ACCDB) can dance and sing with Windows 8 32/64 bit, not only in Test VM but also in live data (production environment). And I was surprised that all applications written on the above-mentioned versions runs amazingly fast compared to Win7 32/64Bit with the same hardware specs. All of my 3rd party ocx’s/dll’s registered and executed without a single glitch. Unlike in Win7 where some of my component failed. My oldest app, a 11-year old POS written in Access 2003 FE and SQL Server 2005 Std BE. I was really2 surprised, So long live Access!

Leave a comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.