[dba-SQLServer] Access BE to SQL

VB.Net is not built in to SQL Server.  The ability to us external 
languages as assemblies (compiled code) is built in.  You still have 
to use VS 2005 to built the functions or whatever and then SQL Server 
can use them.  But, SQL Server/T-SQL can also be used to create 
functions natively.

At 09:40 PM 10/5/2006, you wrote:
>Date: Thu, 5 Oct 2006 22:40:02 -0400
>From: "JWColby" <jwcolby at colbyconsulting.com>
>Subject: Re: [dba-SQLServer] Access BE to SQL
>To: <dba-sqlserver at databaseadvisors.com>
>Message-ID: <005101c6e8f0$ba1c4dd0$647aa8c0 at m6805>
>Content-Type: text/plain;       charset="us-ascii"
>
>LOL, you just want to be prepared.
>
>One thing I have discovered is that man tends to minimize the time required
>to do anything, from changing a tire to painting the house, to writing a
>function or query.  If you are very good at whatever you are doing, you
>often have the experience to overcome this tendency.  Professional painters
>just know how long painting takes, professional developers likewise.  But
>this is not something you are familiar with and JET and SQL Server are just
>different animals.  Thus a simple "multiply by three" might well get you in
>the ballpark.  You will come up to speed eventually.  The first half of any
>given set of tasks will go way slower than that, and the last half will go
>faster.
>
>One thing you might want to consider is moving up to SQL Server 2005.  That
>has the full on VB.Net as the scripting language right inside of SQL Server
>(or so I am told).  While VB.Net and VBA might not be a close match, for the
>kinds of things you might run into it might way better than what is
>available in SQL Server 2K.  As an added bene, when you move the app itself
>to .net, you will already have the core database running on SQL Server 2005,
>and you will be becoming a VB.Net kinda guy.
>
>John W. Colby