>Hi All,
>
> Does anyone know if the change from VB to VB.NET will also be carried over to VBA? Will anywhere that VBA is used need to change to fit the VB.NET Model? It's just a thought I had the other day and I haven't read anywhere about the effects of VB.NET on VBA. I do a fair bit of Office Automation from Both VFP and ACCESS and I'm wondering if the code I've used will still work with Releases of Office post VB.NET. I realise that I probably won't need to worry about this for a while, but it got me thinking.
>
>Regards,
>Gavin...

Visual Studio for Applications (VSA) will be the next step to VBA. Check out the editorial at http://www.devx.com/free/hotlinks/2001/ednote011701.asp