By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
455,887 Members | 1,154 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 455,887 IT Pros & Developers. It's quick & easy.

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

P: n/a
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
around.
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)
Nov 21 '05 #1
Share this Question
Share on Google+
3 Replies


P: n/a
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
datasources.

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

http://www.visual-basic-data-mining....spx?PostID=563

HTH

Nov 21 '05 #2

P: n/a
George,

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
system.data namespace

http://msdn.microsoft.com/library/de...systemdata.asp

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

Adonet
news://msnews.microsoft.com/microsof...amework.adonet

Web interface:
http://communities2.microsoft.com/co...amework.adonet

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.

http://samples.gotdotnet.com/quickstart/

I hope this helps a little bit?

Cor
Nov 21 '05 #3

P: n/a
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

"George H. Slamowitz" <GS********@COX.NET> wrote in message
news:19**********************************@microsof t.com...
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 around.
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)

Nov 21 '05 #4

This discussion thread is closed

Replies have been disabled for this discussion.