I think calling it "Access Database" or "Jet database" may be a little
picky, esp for the original poster who we're trying to help, and not pick at
exact syntaxes.
I'm not going to argue whether you're right or wrong, because ... you are
"right".

And yes, you are right that you don't have to have the program installed to
work with a Jet database. But it makes it much more complicated.
You can create tables through code, and relationships, but my guess is that
most people who are considering using a Jet database, are still at the level
of creating Tables via the GUI of the program, and not via code.

So for the OP, I apologize miscueing on a few of my syntaxes, but I hope my
posts have tried to help your situation.

...

Access...I'm sorry....Jet databases ... are NOT true RDBMS, like Sql Server
or Oracle or etc, etc.

But sometimes they make sense. Or if you plan correctly, you can start
there, but still move up to another database.




"Armin Zingler" <az.nospam (AT) freenet (DOT) de> wrote

Thanks sloan.

Regards

"sloan" <sloan (AT) ipass (DOT) net> wrote

The biggest thing is
"Cost of maintenance".

If you plan out a new application decently, the future costs of adding a
feature, making it support more users will be less, then by keep on hacking
onto an existing Access application.

People think software costs are the development costs. WRONG.
The costs are the maintenance costs.

..Net is the now and future of MS development. You don't want to do a VB6
app (from start) ... and you don't want to create an Access Application.

There is much more wealth of knowledge on the internet about .Net
development. This alone is a benefit. When you need to get something to
work, eventually you will find it on the internet with a dotnet application.

If they outvote you, find another job.




"John" <John (AT) nospam (DOT) infovis.co.uk> wrote

This is not meant as a slight, but if you don't already know the answer to
this question, you are not ready to sell the idea to management.

Moving to .NET is not trivial. The learning curve is incredibly steep. I
must say, however, the results are well worth the journey.

"John" <John (AT) nospam (DOT) infovis.co.uk> wrote

"there is a database, Access" which was nearest to your reply.

Scott is in my idea very correct with his answer. Using Access is more than
using a database, it is a complete enviroment for endusers and developpers
while databases can pretend to be that, however seldom are. Therefore is in
my idea the question not to answer. It relies on what the company wants with
development.

Cor

"Cor Ligthert[MVP]" <notmyfirstname (AT) planet (DOT) nl> schrieb

I don't understand what you wanna say. It was only about the term "jet
database" vs "access database". Call it whatever you want. And I agreed with
"sloan" because he distinguishes between the database file (mdb) and the
database application (Access). That's all I said.


Armin

Cor