I am trying to figure out when it will be important for an Access developer to embrace .net. I guess that is the same as asking when will .net code be mandatory or at least highly recommended for Access? I use Office 2003 and my understanding is that right now, except for managed add-ins, you cannot leverage any .net knowledge when writing VBA code in Access 2007.

Microsoft incorporated .Net into SQL Server 2005, so it would be good to know if you were working in that environment. Generally, everything you want to do with Access you can do with VBA. If you need more than that, then create your interface in .Net and leave Access out of it.

If you know VBA, however, moving to VB.Net is not much of a stretch.


mmcdonal

Look it up at: http://wrox.books24x7.com

Thanks for the reply sorry for my delay reading it.

Can you please explain what you said: "Generally, everything you want to do with Access you can do with VBA."?

Sorry, I meant "VB" as in, .NET.

mmcdonal

Look it up at: http://wrox.books24x7.com

Trust me, there's nothing grand about "dot net" that you'd want to wish it to replace VBA. VBA is the last sliver of sanity in programming, left.

I am looking at all sorts of replacements for VBA since the release of FileMaker Pro 2007... sorry, I meant Access 2007. What a dog.


mmcdonal

Look it up at: http://wrox.books24x7.com