Converting MS Access 2000 application to a VB / VB.NET application



  • 1. Debugging main app with compiled DLL
    Hi, I am debugging a new app using INI functions from a pre compiled .NET dll. When I come to a line calling a function in the DLL, the debugger knows where the code of the dll is and shows it when I use F8 to proceed to the next line of code. I have copied the compiled DLL to the debug folder of the main app and used the 'reference' screen to 'point' to that dll, but it still shows me the dll code. Can anyone tell me how to switch this off because I will be making many many classes with DLLs and I really don't want the debugger to take me constantly to already well debugged code of the compiled DLL. Thanking you in advance Garry
  • 2. How to get all logged on user on a machine
    Hi Gurus, Is there any way to find out all the useres currently logged on my machine. I am using framework 2.0 with VB. I'll appreciate any help I get. Thanks, Steven.
  • 3. Execute macro only for one solution
    Hi all, I have a solution that contains a bunch of projects. When I save a file in any of the projects in this solution, I want to execute a macro that updates the project's assembly version. But I only want this behavior for this one solution. Is there a way to have a Macro that fires for environment events only for a particular solution? (I guess I could have the event handler check to see if this is the desired solution before doing anything, but that's kind of a backward way of going about it. But maybe that's the Zen of macros.) On a related subject: Optimally, I would like to have the macro use some constants defined in an assembly in the solution when it updates the assembly version numbers. This means that the macro needs to have a reference to assemblies in this one solution, which is really tacky. Any thoughts or suggestions? Bob

Converting MS Access 2000 application to a VB / VB.NET application

Postby R2VvcmdlIEguIFNsYW1vd2l0eg » Sat, 26 Mar 2005 22:41:03 GMT

Hello All

I am trying to convert a MS Access 2000 application to a VB application
(Just Started Yesterday)

I am using Visual Studio .NET 2003 utilizing Visual Basic .NET

I think I have a good feel to what I have to do, but does anyone know of a 
GOOD white paper on what is involved, pitfalls, etc?

So far I have run into one problem that I have not been able to figure away 
That is how to access the tables.  In access you have Database objects, 
Recordset objects and all if the associated methods.  I cant seem to find out 
how to convert this to VB.  I have been reading through postings in this 
Discussion Group, but I am still a little bit confused.

Is there a SIMPLE way to access the existing .MDB database tables, and the 
individual fields within the tables.  Any help would be greatly appreciated, 
or a pointer to a good white paper describing the procedure.

Thanks in advance     

George H. Slamowitz
(602) 765-8111
(602) 765-8222 (FAX)

Re: Converting MS Access 2000 application to a VB / VB.NET application

Postby Jerry H. » Sat, 26 Mar 2005 23:32:24 GMT

Heh, some of my co-workers who are absolute Wizards with MS Access, but
are now asking similar questions as yours.  I'd say that, right now,
there isn't really a *simple* way with .NET 1.1, however .NET 2.0
framework will make offer better methods and easier access to

Anyway, you might look here, as this person offers some straight
forward examples:



Re: Converting MS Access 2000 application to a VB / VB.NET application

Postby Cor Ligthert » Sun, 27 Mar 2005 00:57:32 GMT


There is no way to convert a MS Access application to a VBNet application.

However the use of the database itself is very easy to do.

For that you can use ADONET in which are the classes from the so called namespace


Do not mix this up with ADO (ADODB) what is completly different and not 
really a Net part.

For MS Access the best choise to connect and use it is than OLEDB.

In this newsgroup you will mostly be helped with problems about that. 
Another very good newsgroup for that is


Web interface:

When you see samples you see them than as well often for SQLserver they are 
almost (with exceptions from the command.parameters) always the same as for 
msaccess with the difference where an instructions starts for SQL with by 
instance SQLCommand it is for access (OleDB) OleDbCommand

A good place to start is in my opinion.


I hope this helps a little bit?


Re: Converting MS Access 2000 application to a VB / VB.NET application

Postby Dean Slindee » Thu, 31 Mar 2005 12:09:51 GMT

You need to decide one important point first: is the data going to stay in
.mdb tables?

If yes, then you can use VB.NET calling ADO recordsets (not ADO.NET
datasets)  This is Not progressive thinking in .NET land, but it works.

If no, then consider upsizing the Access application backend from .mdb to
SQL Server tables.  Access has an internal tool to do this.  You will need
to convert Access queries into SQL Server stored procedures that can be
called from VB.NET.  The stored procedures can also be the recordsource for
the upsized Access front-end (should you decide to retain it for some
reason, or for an interim period).

I have done all of the above over the past several years, and they all work.
Dean Slindee


Similar Threads:

1.VB 6 Application with MS Access 2000 backend for Windows 2003 Server

HELP!!! everyone,

I have a VB 6 application that uses Microsoft Access 2000 as the
backend database. They say it requires MDAC 2.6 Sp2.  This application
is currently running fine on a Citrix server running Windows 2000
server. I have to migrate my citrix farm and so am upgrading to
windows 2003 server and a newer version of citrix.  However, when
trying to install this one application that 30-40 users use, I recieve
the following error.

<----------Beginning of Error-------------->
MDAC 2.6 Sp2 cannot be installed on this machine. MDAC 2.6 Sp2
requires any one of the following configurations:

Microsoft Windows 95 or 98 with Y2K update 2 and Internet Explorer
4.01 SP2 or later
Microsoft Windows Millenium
Microsoft NT 4 SP5 (or greater) and IE 4.01 SP2 or later
Microsoft Windows 2000

Setup will exit now. Please restart setup after installing the
necessay updates to this machine.
<------End of Error----->

I spoke with the vendor and they said that other IT departments might
have gotten it too work on Windows 2003 with some minor tweaks. They
said that it was developed in VB 6 with Access 2000 as the backend and
that MDAC 2.6 Sp2 was a requirement.

I installed Access 2000 on the new Windows 2003 Terminal Server and
have tried both MDAC 6 SP2 and MDAC 7 before trying to load the app
but still get the same error message without any luck.

Is there anyone out there that might might have some ideas on how to
get this app to work with some tweaks?   I would appreciate your


2.access 2000 scurity in application

Appreciate help.

 How could I lock an access database in a db application where I used
Access 2ooo?
 (I mean lock it so the user can't change or even may not
see the db table?)


3.Converting a VB.Net Console Application to Web Service application

Hi All,

  I have written a simple VB.Net Application which takes a .pst file and 
extracts the messages attachments from the .pst. It is working fine as a 
Console Application.

  I tried Web Service enable this App and it is giving me the 500 Error. 
When i tried debugging it the IE browser shows up the operations exposed by 
the Web Service and i am entering the path to the pst file and when i hit 
invoke i am getting the Error at the Line which reads  as 

 Dim myNameSpace As Outlook.NameSpace = objOutlook.GetNamespace("MAPI")

  Could you guys pls let me know how can i resolve this..

Thanks a lot


4.Is there a way to convert MS Access 97 databases to 2000 format in VB

5.Converting ASP VB .NET Web Application to VB .NET Executable Question

I have created several VB .NET web applications and will soon have to
start building "real" executables.  This may be involved, but how much
conversion is in a path like this?  Is it simply recreating the GUI,
give the GUI controls the same name as in the web app and place the
code in different events than the ASP .NET page?

For example, I have an ASP.NET VB.NET web page, uses a database, etc.
The datagrid control, some textboxes, all that.  There are events and
code in those events.

I need to take that page and turn it into an executable.  Is this
huge, or is this more manageable because of the .NET platform?

Thank you.

6. Get a value of a VB.Net application from another VB.Net application

7. Deploying VB .NET application WITH MS Access db

8. Running MS Access Application From 2003

Return to VB.NET


Who is online

Users browsing this forum: No registered users and 56 guest