[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


_______________________________________________
dba-SQLServer mailing list
dba-SQLServer at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
http://www.databaseadvisors.com