Results 1 to 5 of 5
  1. #1
    Join Date
    Dec 2004
    Location
    Madison, WI
    Posts
    3,926

    Unanswered: 4GL versus MSAccess

    Does anybody have the REAL scoop on 4GL programming versus vba/vb? My new company is very PRO-4GL and very ANTI-MSAccess/VB.
    Expert Database Programming
    MSAccess since 1.0, SQL Server since 6.5, Visual Basic (5.0, 6.0)

  2. #2
    Join Date
    Sep 2003
    Location
    MI
    Posts
    3,713
    Quote Originally Posted by pkstormy
    Does anybody have the REAL scoop on 4GL programming versus vba/vb? My new company is very PRO-4GL and very ANTI-MSAccess/VB.

    4GLs ... Think of Crystal Reports or any other "high level" "programming" language .. They do have their good points:

    Rapid Development
    Usually low learning curve
    Anyone can think their a programmer
    Bells and whistles

    Drawbacks:

    Can be limited on intricate/complex tasks
    Can do the simple shit for the most part
    REAL programmers sneer at 4GLs
    Anyone can think their a programmer

    But, the 1st one is the most important. Some of the 4GLs just can't do very sophisticated/intricate work ...
    Back to Access ... ADO is not the way to go for speed ...

  3. #3
    Join Date
    Dec 2004
    Location
    Madison, WI
    Posts
    3,926

    4gl

    Thank you very much M Owen! What would be an example of an intricate/complex task which couldn't be done in 4GL? (The 4GL programmers are consistently telling me "Anything MSAccess/VBA/VB can do we can do just as easily with 4GL") So far, 4GL really disgusts me (but I've been a vba programmer for 15 years now and I haven't seen any "Bells and Whistles" with 4GL.)
    Expert Database Programming
    MSAccess since 1.0, SQL Server since 6.5, Visual Basic (5.0, 6.0)

  4. #4
    Join Date
    Nov 2003
    Location
    Sussex, England
    Posts
    404
    I tried 4Gl and ran it through some tests. Referential integrity, easy to set up on the graphical interface, but what happens if you do it wrong?

    I tried this. With Access it's very difficult to put the relationship the wrong way round, but not so with 4GL. It's also very difficult to correct this sort of mistake with 4GL.

    I made a lot of other 'mistakes' to try it out, and frankly I wasn't impressed with it as a serious development tool.

    ODBC support? (The version I had didn't support ODBC which made it a worthless tool at best.)

  5. #5
    Join Date
    Sep 2003
    Location
    MI
    Posts
    3,713
    Quote Originally Posted by pkstormy
    Thank you very much M Owen! What would be an example of an intricate/complex task which couldn't be done in 4GL? (The 4GL programmers are consistently telling me "Anything MSAccess/VBA/VB can do we can do just as easily with 4GL") So far, 4GL really disgusts me (but I've been a vba programmer for 15 years now and I haven't seen any "Bells and Whistles" with 4GL.)
    Depending on the 4GL, an intricate task may be using multiple temp tables ... Or some types of queries are not supported. Complex task can be as simple as having a routine that collates data from multiple tables into a single table for reporting ... Some 4GLs only allow a primary query and/or table ...
    Back to Access ... ADO is not the way to go for speed ...

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •