Decision to convert

[Guest]

I have created a program is MS Access which allows me to create text output
that is readable by our mainframe (main purpose). This process includes
running cutome queries what are appended to formated tables and then these
tables are output to text. I would like to migrate this program out of Access
to a stand alone application that anyone could run. My question is should I
leave the database native to Access and Visual Studio to create the front
end? Or should I completely re-create my program in Visual Basic? Any ideas?

 

[Rick Brandt]

I have created a program is MS Access which allows me to create text
output that is readable by our mainframe (main purpose). This process
includes running cutome queries what are appended to formated tables
and then these tables are output to text. I would like to migrate
this program out of Access to a stand alone application that anyone
could run. My question is should I leave the database native to
Access and Visual Studio to create the front end? Or should I
completely re-create my program in Visual Basic? Any ideas?

I don't understand. You'll need a database of some kind right? Are you
contemplating writing your own database engine? Applications written in
just about any programming environment that manipulate data will do so by
interacting with an existing database technology like Access/Jet or SQL
Server.

If you store your data in a Jet database (MDB file) then you can work with
that data without using Access (the program). Is that the question? Whether
you need to use the Access program to work with an "Access" database? If
so, the answer is no. Lots of programs use Jet files as their database and
do so without the Access program. All you need are the Jet dlls (MDAC) to
work with data in an MDB file.

 

[Guest]

Hi Rick

My query is whether to leave my program in MS Access or to reconstruct it in
a more stable environment like a stand alone VB application. I can construct
my tables in any database like SQL or Oracle, However, I have done alot of
work with queries, reports and macros in MS Access. Is it worth leaving in MS
Access (the process no the database tables)

 

[Rick Brandt]

Hi Rick

My query is whether to leave my program in MS Access or to
reconstruct it in a more stable environment like a stand alone VB
application. I can construct my tables in any database like SQL or
Oracle, However, I have done alot of work with queries, reports and
macros in MS Access. Is it worth leaving in MS Access (the process no
the database tables)

Why would you consider a VB front end "more stable"? Writing your front end
will take LOTS more time in VB especially considering that you already have
written it in Access and you would essentially be starting over from
scratch.

If the jist of your question is "What makes a better database front end,
Access or VB?" and you are asking the question in an Access Newsgroup what
sort of responses do you expect you will get?

VB is a general purpose development tool. Access is specifically geared
towards database interaction. Yes, it is easier to create something that is
more "stand-alone" with VB, but again at the cost of a lot more work to get
the same functionality.

 

[Guest]

The stability of an Access based application is dependent more on the skill
of the developer than the capabilities of Access. The same would be true of
VB or any other developement tool.

You are sounding like one of those mainframers who thinks Access or anything

 

[David W. Fenton]

Lots of programs use Jet files as their database and
do so without the Access program. All you need are the Jet dlls
(MDAC) to work with data in an MDB file.

Er, the MDAC has not included the Jet DLLs for several years now.

 

[David W. Fenton]

My query is whether to leave my program in MS Access or to
reconstruct it in a more stable environment like a stand alone VB
application.

The only reason Access has ever had a reputation for "instability"
was because when it's used with Jet data by someone who doesn't know
what they are doing, the Jet data often get corrupted.

If you're not using a Jet back end, there is *no* instability
involved with Access.

There is only requirement for having Access installed or the Access
runtime.

Michael Kaplan did work a long time ago to compare the actual
workset (i.e., the amount of memory used, the number of DLLs loaded,
etc.) when using Access or an Access runtime vs. a VB front end, and
he found that the difference was very small.

And an Access app is *much* easier to create.

Seems like a complete no-brainer to *me*.

 

[Rick Brandt]

Er, the MDAC has not included the Jet DLLs for several years now.

True, but a version of MDAC that does include them is still available as a
download.