Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I said this in a comment, but I'll repeat it as an answer:</p> <p>If you look at the future of Access, it's bright. MS is investing a lot in it. Access 2010 in conjunction with Sharepoint 2010 offers some pretty amazing benefits, and you do it all without any VBA (instead you use the new, powerful macros, which have variables, branching and error trapping). You can do this with client Access and no Sharepoint, or you can publish it to Sharepoint and the app runs in the web browser.</p> <p>My surmise is that one of two things are going to happen in regard to the programming language in Access in the timeframe of the 2-3 Access versions after 2010:</p> <ol> <li><p>VBA remains supported and all the work goes into macros. Eventually, macros become the preferred method for all programming in Access, with VBA eventually deprecated and finally eliminated. Because by that point macros are so versatile and robust, not programming language will replace VBA. </p></li> <li><p>the same scenario, except that .NET is phased in as a replacement for VBA.</p></li> </ol> <p>I would hope for #2, but it depends entirely on Microsoft's view of what Access is, i.e., primarily and end-user tool with upward extensibility (#1) or both an end-user tool and a versatile development tool with unlimited extensibility (#2).</p> <p>My point is that you can stay with Access, avoid VBA for now (if you really hate it), and probably end up with a workable, stable app.</p> <p>However, my reservations about macros are very strong, in that I find them very difficult to maintain because of their standalone nature. VBA code is pretty easy to navigate and understand, because it's compiled and because there's a full-featured IDE. Macros are much more compartmentalized and difficult to trace interrelationships between them and the objects they are used in. Add in the embedded macros added in A2007 and it gets even more complicated. I don't know if the Access team is addressing this or not, but for me it's a real step backward in terms of manageability, particularly if the beefing up of macros ends up causing VBA to be deprecated and then not replaced with a correspondingly powerful programming language with a good IDE.</p> <p>Last of all, I've said nothing about the database engine, since Access is completely agnostic on this regard, able to use Jet/ACE to start with and then to upsize to the engine of your choice. It's a non-issue, seems to me, since your options are wide open when using Access as your front end.</p>
    singulars
    1. This table or related slice is empty.
    1. POwanting to move up from ms access, thinking .net? visual studio?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USDavid-W-Fenton
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COi wish they would have phased in .net a few versions ago. everything i've seen thats written in .net is beautiful and fast. i didn't know macro's were now favored over vba (i have beta 2010) -- i'll take a look -- right now i have quite a bit of vba code but, and this is one of the reasons im itching to move to something else -- most howto's for stuff i've been looking up were written for .net
      singulars
      1. PO
      1. USTristan Lear
    2. COI will say that since we get a 64 bit version of VBA in access 2010, then some real investment has occured in VBA. So, there certainly nothing yet that says a "lid" is being put on VBA.
      singulars
      1. PO
      1. USAlbert D. Kallal
    3. CO@Tristan Lear: I didn't state that macros are favored. I suggested that they might one day be. And the "beauty" of .NET is in the eye of the beholder. For most desktop database applications, it looks to me like using a bulldozer to plant marigolds.
      singulars
      1. PO
      1. USDavid-W-Fenton
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload