John Colby
jcolby at colbyconsulting.com
Tue Oct 7 12:27:37 CDT 2003
Robert, I have programmed since the 80s, using Fortran, C, Turbo Pascal, VB, DBase XX, Paradox, Access etc. Access is in no way even remotely equivalent to any of those other tools. Access is a tool just like C#, C++ or even VB. Access was designed, from the ground up, to build databases and the application to use the databases. C, and later C++ was designed, from the ground up, to give you gnats ass control over hardware. It was designed to do what assembler allowed, but from a higher level. VB was designed to replace Fortran as a general purpose, easy(ier) to use language for general purpose programming. Anyone who makes any attempt to claim that C or ANY of it's variants is a RAD database development tool appears to ME to fall into that circle where people ask others to flog them so they can enjoy the pain. Using JUST Access I built (last week), from the ground up, a database with 20 tables, 19 relationships, enforcing referential integrity, 16 forms, including tab forms displaying child records to one of the tables, combos that provide pick lists from the list tables etc. etc. ALL of that took ~12 hours. If you claim that you can do that in C, C++, C# or VB I will: a) Take my hat off to you OR... b) Call you a liar to your face and challenge you to do so in front of me. Probably the latter. I can do this in front of you BTW (assuming we can meet face to face). So... >Wow, so choosing the right tool for the job is as bad as body piercing, whips and chains? NO, choosing the WRONG tool for the job is the equivalent of body piercing, whips and chains. And further, I was making a joke, so lighten up a bit. John W. Colby www.colbyconsulting.com -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com]On Behalf Of Djabarov, Robert Sent: Tuesday, October 07, 2003 9:43 AM To: dba-sqlserver at databaseadvisors.com Subject: RE: [dba-SQLServer]ODBC connection - Is this normal Wow, so choosing the right tool for the job is as bad as body piercing, whips and chains? AND, you dare to call it "framework"????? "On-The-Fly SQL Statements"???? Man, I must be missing something very simple, and wasted all my life not being able to see it...wonder what the heck it is... Oh, I get it, it's MS Access used as a RAD tool!!!! Good luck -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of John Colby Sent: Tuesday, October 07, 2003 2:17 AM To: dba-sqlserver at databaseadvisors.com Subject: RE: [dba-SQLServer]ODBC connection - Is this normal >> Very normal. It's also normal to drop Access as your FE and do everything using something more robust like C#, C++, or even VB. Yea, in the same circles where it is normal to tie each other up, pierce body parts and use whips and chains for sexually deviant purposes. >Or even abandoning the .mdb part of Access and building it as an ADP, >then that problem goes away completely and you still retain some of the RAD attributes of building it w/ Access. True. And for those of you who don't use a framework, or who designed their framework from the ground up to use SQL Server that is certainly an option. My framework does things not easily ported to SQL Server (on-the-fly SQL Statements referencing form controls for example). One of the reasons that I moved my billing app to SQL Server is to slowly start the process of porting the framework. To this point, life has gotten in the way of THAT project. John W. Colby www.colbyconsulting.com -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com]On Behalf Of Francisco H Tapia Sent: Tuesday, October 07, 2003 1:10 AM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer]ODBC connection - Is this normal Djabarov, Robert wrote: > Very normal. It's also normal to drop Access as your FE and do > everything using something more robust like C#, C++, or even VB. > Or even abandoning the .mdb part of Access and building it as an ADP, then that problem goes away completely and you still retain some of the RAD attributes of building it w/ Access. -- -Francisco