Pretty broad, indeed.
VB6.0 dll's are made to compile into COM objects, which are generally easy
to call from Access -
although Access gets a bit finicky about the visuals of ActiveX controls
from VB.
If you just want to write calculations, etc in your dlls, you should be
fine.
VB.NET uses a different paradigm from COM for its parts to talk to each
other.
That works great within pure .NET applications, and makes deployment a snap.
However, if you want to call a VB.NET object from "non-managed" code (e.g.
Access), you must make it into a COM object. VB.NET has a couple of wizards
which will do this for you in a couple of different ways -
any "expertise" I may have here gets pretty thin at this point.
I've done it and had it pretty much work, although personally I'm still
struggling with getting events and exceptions across the divide.
Now if you want to have your VB6.0 or VB.NET application call Office
operations, that's a whole different question...
But to get back to your general question -
as long as your VB6.0 or VB.NET "application" exposes a COM interface,
you can set a reference to it in your Access code and interact with that
interface.
HTH
- Turtle
"Maur" <pk***@earthlink.net> wrote in message
news:k5****************@newsread2.news.atl.earthli nk.net...
Thanks, Turtle.
So any reference to VB6 or VB.net would work with any Access
(97,2000, XP) application -- front end ?
(I realize that this is is a broad and sweeping statement
on my part. Essentially, that is my question.
Maur
"MacDermott" <ma********@nospam.com> wrote in message
news:%B******************@newsread1.news.atl.earth link.net... I know of no problems in having Visual Studio 6.0 and
Visual Studio.NET installed on the same computer.
In fact, I am now developing an application with a VB 6.0
"Front End" which calls a VB.NET dll.
The two Visual Studios are totally separate applications.
HTH
- Turtle
"Maur" <pk***@earthlink.net> wrote in message
news:a7****************@newsread2.news.atl.earthli nk.net... I have Office XP Pro and Developer Edition and SQL Server installed on my local development machine.
Given the option of installing;
Visual Studio 6.0 Enterprise Edition
AND/OR
Visual Studio.NET Enterprise Architect Edition.
I would prefer to move forward with the .NET but ...
My question is if I use the VS.NET can I design VB.Net
code or standalone modules to be compatible or interact with existing Access Databases/Office 2000 and Office XP and
Office XP Developer Edition?
I do not have any critical apps that would need to be
upgraded. I just want to write new components and class
modules to let them be used in Access and SQL server apps.
Is it okay -- even advisable to have VS6 and VS.Net
installed on a single local machine with one partition?
I need to install one of these soon. My main use will be VB for now but web apps later. Your thoughts are most
appreciated.
Thanks,
Maureen
