Search results

  1. C

    Hope to contribute

    I generally agree...SQL is and should be easy. I'm often torn between building a long fancy SQL string vs. using the clarity provided by the Access VBA recordset and its methods...I like a powerful SQL string but it's awful ugly in your code...the recordset object makes better looking code but...
  2. C

    Hope to contribute

    Started out doing strictly Access QBE queries but I taught undergrad Intro Databases and had a T-SQL contract so I got the chance to hone my SQL skils...but always more to learn. Happy to share given how much I've learned from these types of communities.
  3. C

    Hope to contribute

    Good question: I'd say I enjoy making useful UX's but I'm full-stack so I do it all...some things better than others obviously. I can model anything with tables and relationships (i.e., ERDs), I can do anything I want in SQL but Access doesn't do CTEs so I tone it down in there, love VBA for...
  4. C

    Hope to contribute

    My clients and I are using Access for Office 365
  5. C

    Hope to contribute

    Hi, I was "forced" to learn Access development back in 1995 with Access 2.0. Since then, other techs have come and gone, Access and Office Dev is the one constant throughout my career so far. I would have never predicted. Looking forward to sharing Access and database knowledge folks!
Back
Top Bottom