469,322 Members | 1,157 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,322 developers. It's quick & easy.

VBA code in a VB.Net application

Hello

We have a VB6 application that integrates an VBA IDE from which the final
user can make modifications.

We want to pass the application to VB.NET, and the first step, before
rethinking the whole application, is to pass the conversion wizard and see
how it goes.

But we want to keep those client VBA modifications working with the least
changes made to them. I've tried integrating VBA in a .NET project but when
I make the VBA IDE visible, I get a COMException ( ErrorCode -2147220119).
The same happens when I converted the VB integration sample of the VBA SDK
to .NET.

I've read that VSA is the substitute to VBA in .NET, but besides I'd have to
tell to all my clients to change all their VBA code to VB.NET code, the last
post I've read about VSA says that the project is dead and to forget about
it.

Anybody was able to integrate VBA (code and IDE) in a .NET app?
Any problems with Interop.MSAPC? Do I have to do it manually?
Is VSA dead?
What are the plans of Microsoft for VBA (or it's substitute)? Which is the
way I should follow?

Thank you very much

Igor Mendizabal
R.P.S.
Jul 21 '05 #1
1 1615
Igor,

I do not know the answer however a lot of crossposting (no problem) where I
see not in the newsgroups..

microsoft.public.dotnet.languages.vb (one of the three most active
developper newsgroups)
and in my opinion a good one for your question
microsoft.public.dotnet.languages.vb.upgrading (with the same people active
as in the one above)

When you get not a right answer you can maybe try it in one of those.

I hope you get your answer.

Cor
Hello

We have a VB6 application that integrates an VBA IDE from which the final
user can make modifications.

We want to pass the application to VB.NET, and the first step, before
rethinking the whole application, is to pass the conversion wizard and see
how it goes.

But we want to keep those client VBA modifications working with the least
changes made to them. I've tried integrating VBA in a .NET project but when I make the VBA IDE visible, I get a COMException ( ErrorCode -2147220119).
The same happens when I converted the VB integration sample of the VBA SDK
to .NET.

I've read that VSA is the substitute to VBA in .NET, but besides I'd have to tell to all my clients to change all their VBA code to VB.NET code, the last post I've read about VSA says that the project is dead and to forget about
it.

Anybody was able to integrate VBA (code and IDE) in a .NET app?
Any problems with Interop.MSAPC? Do I have to do it manually?
Is VSA dead?
What are the plans of Microsoft for VBA (or it's substitute)? Which is the
way I should follow?

Thank you very much

Igor Mendizabal
R.P.S.

Jul 21 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

11 posts views Thread by Peter Steele | last post: by
6 posts views Thread by Dan McCollick | last post: by
8 posts views Thread by neilmcguigan | last post: by
7 posts views Thread by Jay | last post: by
reply views Thread by suresh191 | last post: by
reply views Thread by Gurmeet2796 | last post: by
reply views Thread by mdpf | last post: by
reply views Thread by harlem98 | last post: by
reply views Thread by listenups61195 | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.