Quote:
|
quote:how can we use VB.net Code in access forms??
|
You can't at this point (as of VS.NET 2K3, can't speak about 2K5), and my suspision is that Microsoft won't be moving in that direction. They seem to be headed the other way: making Office functionality available to .NET assemblies, not integrating Common Language Runtime supported languages (C#,
VB.NET, etc.) into Office. But who knows. For example, Visual Studio Tools for the Microsoft Office System enables you to create .NET projects that use Word and Excel functionality (no support for Access as far as I know). I havn't played with it yet, but I think installing the Tools on your system creates a new project type in VS.NET IDE: Microsoft Office System Projects, which enable you to use classes in the Microsoft.Office.Core namespace:
'
VB.NET
Imports Office = Microsoft.Office.Core
// C#
using Office = Microsoft.Office.Core;
Again I'm not sure, but I heard SQL Server 2005 was going to integrate support for some CLR supported languages, allowing you to write, say, stored procedures using
VB.NET or C#. Don't know if that happened or not. Just ain't buyin' the new stuff the day it comes out like I used to.
But as far as Access is concerned, only the Jet engine (which, of course, isn't Access) can play a role in a .NET solution as a backend data store. Otherwise, Access and .NET don't speak to each other.
Bob