Conference abbott::visual_basic

    >If I wanted to write an app in (say) VB3 using ACCESS as its d/b
    >engine, could I write the same app in ACCESS/VBA instead?
    
    Well, the first point to note is that you're rather behind the times.
    I've been using VB5 for the last month. VB5 is no way comparable to VB3
    in terms of useability, scalability, features, etc., etc.
    
    As to your question as to whether Access v7 (or were you meaning v8 in
    Office 97?) is a better development tool than VB3, I think it depends
    on what you want.
    
    If you want to write internet or intranet enabled applications then
    neither is suitable. You really want to use VB5.
    
    If you want to write a small database app for keeping track of your
    library of books, CDs, videos etc. then Access is fine.
    
    If it's for a large multi-person project with code sharing,
    co-ordination of development, a requirement for maintainability of code
    by people other than the original authors, then go with at least VB4
    plus Visual SourceSafe.
    
    If you want to write something that only you can maintain then you can
    probably do that in VB3, but it's a lot easier in Access. So for job
    protection stick with Access.
    
    On the other hand if there is any danger that the db needs will
    escalate out of reach of Access and you have to upgrade to something like
    SQLServer then go with VB3 (of course VB5 would be far better). That
    way you won't lose your job when your Access app is thrown on the
    scrapheap and some other department wins the bid to do the
    Corporate-wide product with their proposal to use more scalable,
    maintainable, more uptodate technology.
    
    In short, Access is fine for a small Mom&Pop outfit with small needs,
    one person doing the development and later support and maintenance, but
    is not a serious development option for medium to large-scale projects.
    
    Cheers,
    Brian

    
    Althought it's rather obvious it's worth noting that to use an
    application written with Access/VBA you need Ms-Access. However, and
    I'm sure Brian will happily correct me if I'm wrong, using VB you
    don't. Hence you can simply distribute the application and database
    file without the end-user having the additional expense of purchasing
    Ms-Access.
    
    If this isn't the case then use Delphi and ODBC 'cause I can do it with
    that.
    
    Chris

I use  many features of VB extensively (e.g. Class Modules) which are 
not available at all in Access.

But I find Access is good for prototyping things quickly which eventually 
end up being implemented in VB4/VB5.

    re .2
    
    I believe with the Access Developer's Kit you can get the same setup as
    VB, ie you can build an application and just distribute the libraries.
    That way the only way the user can use your application database is via
    the application unless they go out and buy Access themselves. So Access
    plus the ADK is just as good as VB from the point of view of
    distributing the application.
    
    This question is an old chestnut which crops up almost every time there
    is a new release of one or the other. I remember when VB3 came out with
    the ability for the first time to create Access databases and tables
    programatically. Then the question was the other way round. If you have
    VB why do you need Access?
    
    The point is that Microsoft's marketing is second to none. There are
    always key elements in one but not the other. You need Access even if
    you've got VB (regardless of the versions) because:
    
    1) It's just so much easier to design and build your database in Access
    than in VB
    
    2) There are some nifty things in Access which aren't in VB like
    security.
    
    As already pointed out there are lots of key features in VB,
    particularly VB5, which are missing from Access which are necessary for
    serious development. So Microsoft win. You end up going out and buying
    both.
    
    Cheers,
    Brian