Re: VBA/VB6 vs VB.net
- From: "Douglas J. Steele" <NOSPAM_djsteele@xxxxxxxxxxxxxxxxx>
- Date: Tue, 3 Jan 2006 06:22:42 -0500
You cannot use VB.Net instead of VBA in Access. However, can you not create
an ActiveX COM object out of your VB.Net application and use it in VBA? You
could have done the same in VB6, so that you wouldn't have had to import the
code into Access at all: you'd simply have had a reference to your VB6 EXE
or DLL.
--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)
"GPO" <GPO@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:DE10CBE1-2651-452A-9D62-A2F895D8722F@xxxxxxxxxxxxxxxx
>A few years ago my mate and I developed a neato little program in VBA/VB6
> that could run either as a MS Access 2000 (or later) mdb application, or
> as a
> VB exe that linked to a SQL Server database.
> The bulk of the code in either case was common. We just exported the
> relevant modules from VB6 and imported them into Access. We even had an
> SQL
> parser that would convert tSQL into an SQL dialect that access could run.
> All
> up it meant you could maintain the two as if thery were a single app,
> making
> changes in one place to update both.
>
> Now the people who manage the corporate direction of programming in our
> organisation have said that all VB6 apps have to be converted to vb.NET.
> That
> on it's own is bad enough, but my question is this: Does Microsoft offer
> the
> same seamless integration between an Office scripting language and VB.net
> as
> it did with VBA/VB6? If we cannot keep common, the code that should be
> common, then we essentially now have two apps to maintain, and all the
> problems that go along with that.
>
> Has anyone else dealt with this before?
.
- Prev by Date: about access 2003
- Next by Date: RE: 5 access 2000 users and 1 AccessXP user
- Previous by thread: about access 2003
- Next by thread: RE: 5 access 2000 users and 1 AccessXP user
- Index(es):
Relevant Pages
|
Loading
