[dba-SQLServer] OLEDB

SQL+VB/VB.net+ActiveReports

Robert Djabarov
SQL Server & UDB
Sr. SQL Server Administrator
Phone: (210)  913-3148
Pager: (210) 753-3148
9800 Fredericksburg Rd. San Antonio, TX  78288
www.usaa.com

-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of
Francisco H Tapia
Sent: Thursday, April 08, 2004 4:01 PM
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer] OLEDB

Until recently (and I havent used them) VB.net had the limitation that 
it has no reporting resource except for the Crystal8 that comes w/ it 
and it's my opinion that it's pretty crappy.  However now there's 
reporting services for Sql Server 2000 and if you have the Sql Server 
license then the reporting services is free(AFAIK).  Access for me at 
least continues to be the best bang for the buck in the sense that you 
have a gui/reporting tool all in one.  But fwiw, Acess still has some 
minor quirks in the way it likes to handel connectivity.  I'm looking to

upgrade to Access 2003, have the disc and all but am worried to install 
it on this pc because of what it might mean in terms of breaking 
things... will Access 2000 still work?

Charlolette posted a cool upgrade tool called evolution, that could 
upgrade your Access fe to VB.net... it's 80 bucks and if it really 
worked, I'd LOVE to buy it.but I digress.  SqlServer developers may be 
fine w/ having a linked table solution or some manner in which the 
tables are exposed.  This leads to sloppy front ends.  You are really 
not leveraging the power of SqlServer because you won't be using 
sprocs.  However any hired Sql DBA may not even want the job when he 
finds out the base tables are exposed.  The rule of thumb, you keep the 
users out of the tables.  You provide the developers w/ Views and 
sprocs.  That's the only way at getting at the tables... and it does 
make it for more work as now you have to not only port the tables, but 
also the queries and in many ways the method in which you "think" about 
a query since now most if not all of the work is passed on to SqlServer.




Martin Reid said the following on 4/8/2004 1:31 PM:

>ADP
>
>But what if it was a straight forward linked table solution??
>
>Just looking for opinion?
>
>MArtin
>
>
>----- Original Message ----- 
>From: "Mike & Doris Manning" <mikedorism at adelphia.net>
>To: <dba-sqlserver at databaseadvisors.com>
>Sent: Thursday, April 08, 2004 9:10 PM
>Subject: RE: [dba-SQLServer] OLEDB
>
>
>  
>
>>Access ADP or VB.Net with SQL Server drivers
>>
>>Doris Manning
>>Database Administrator
>>Hargrove Inc.
>>www.hargroveinc.com
>>
>>
>>-----Original Message-----
>>From: dba-sqlserver-bounces at databaseadvisors.com
>>[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of
Martin
>>    
>>
>Reid
>  
>
>>Sent: Thursday, April 08, 2004 3:24 PM
>>To: dba-sqlserver at databaseadvisors.com
>>Subject: [dba-SQLServer] OLEDB
>>
>>
>>You have moved your databases up to SQL Server. What would you use for
the
>>front end connection, for example would you change to OLEDB??
>>
>>    
>>


-- 
-Francisco


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