What MS Access version to use?

[Tomislav]

Hi,

I would like to use MS Access as database for my application. Program will
be made in VS 2005. What MS Access version is best to use, 2003, 2002, 2000?
What version do you reccomend?

Thanks very much,
Tomislav

 

[Douglas J Steele]

If you're going to be using VS 2005 to build the application, you're not
really using Access, you're using a Jet database.

All three of the versions of Access you list use the same version of Jet,
4.0, so it doesn't really matter.

 

[Craig Alexander Morrison]

If you are using VS2005 have you considered using SQLS2005 - they are
designed to work together.

If you download an Express Version of VS2005 (VB, VC++, VC#, Java or Web
Developer) you will get SQL Server 2005 Express thrown in.

SQL Server 2005 Express is also available as a standalone download.

As already explained you are not using Access if you are only using a
Database containing just tables and relationships, this is actually Jet.

The current version is Jet 4.0 (SP8).

 

[Tomislav]

Thanks Craig,

If you are using VS2005 have you considered using SQLS2005 - they are
designed to work together.

I don't know how difficult is to install/deploy application with SQL 2005
Express, and what operating systems are supported with SQL 2005 Express. I
would like that my app works also under Windows 98 (although this is old
operating system, but still some users have it), Windows 2000, Windows XP
Home and Proffesional.

Thanks very much,
Tomislav

 

[Brendan Reynolds]

Apparently SQLS 2005 requires Windows 2000 SP4 or later ...

http://www.microsoft.com/downloads/...b5-0b07-4448-8848-dcc397514b41&displaylang=en

Of course, your client app could still run on Windows 98 if the Windows 98
PC can connect to a suitable server.

 

[dbahooker]

dont use MDB for anything
use SQL express or MSDE

 

[Tomislav]

Thanks,

dont use MDB for anything
use SQL express or MSDE

Do you have real reasons why not using MS Access (JET 4.0)?. Consider this
is rather small application, and my goal is that application deploys easily,
and that I dont have to install SP2 on Windows XP or SP4 on Windows 2000.

Thanks very much,
Tomislav

 

[Tony Toews]

Do you have real reasons why not using MS Access (JET 4.0)?. Consider this
is rather small application, and my goal is that application deploys easily,
and that I dont have to install SP2 on Windows XP or SP4 on Windows 2000.

I can't see the person to whom you are replying but I suspect it's an
Aaron Kempf. If so he has a real problem with the MDB format for
reasons which are blindingly obvious to himself. Unfortunately, in
most cases, the reasons don't make sense to others.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm

 

[TC]

I thought you'd agreed to stop slagging off at MDBs.

TC [MVP Access]

 

[Brendan Reynolds]

The .NET Framework 2.0 requires Windows 2000 to be updated to at least SP3,
and Windows XP to be updated to SP2 ...

http://www.microsoft.com/downloads/details.aspx?FamilyID=0856eacb-4362-4b0d-8edd-aab15c5e04f5

.... so if you're targeting that version of the framework, you'll need to
deal with the SP issue anyway. I don't know whether VS 2005 allows you to
create apps that target an earlier version of the framework?

 

[dbahooker]

tony

so glad to flame you again

yes; MDB is crap and anyone that uses it is a sissy

these MVP sissies are too wimpy to even learn SQL Server; so i woudln't
listen to them at all.

First and Foremost; im not sure that it's SECURE to use Access 97.

In fact; if i had a cusomter that didn't have XP SP2-- do you know what
i would tell them?

i would tell them to go and screw themselves; if they dont' care enough
about Windows to keep it patched; then im not going to spend my time
building solutions for them.

BECAUSE IT'S IMPOSSIBLE TO SECURE WINDOWS WITHOUT RUNNING
WINDOWSPDATE.MICROSOFT.COM _AND_ OFFICEUPDATE.MICROSOFT.COM

if it's impossible to secure windows; u shouldn't have your computer ON
because you WILL be compromised.

even in REDMOND-- even MICROSOFT can't prevent a single machine from
getting compromised.

I used to work in Corporate Security.

We couldn't install WINDOWS fast enough to patch it to not get
compromised.

so people that dont get patches? screw them in the mouth.

 

[TC]

yes; MDB is crap and anyone that uses it is a sissy

So that would include YOU:

"i have worked on a hundred applications ... in MDB"


http://groups.google.com/group/microsoft.public.access/msg/16e704036c9b1ae8

TC

 

[dbahooker]

yes because im sick and tired of the same old piece of shit application

im tired of updating linked tables, refreshing; odbc-- all that crap

ADP is a much much better solution for a hundred reasons

 

[TC]

yes because im sick and tired of the same old piece of shit application

No, you're sick and tired of making the same old errors that you always
make. No-one else has the problems you mention, because everyone else
knows how to use the product properly. I've told you all of this
before, but it seems I have to tell you again:

im tired of updating linked tables,

Any competent Access developer writes code to do that automatically. Or
you can download suitable code from the web. You obviously just don't
know how to do it properly. The problem here is nothing to do with
Access, at all. It's to do with your own personal ignorance of how to
use the product properly.

refreshing

Refreshing what? I spend /zero/ time "refreshing" anything. No-one else
here spends any time "refreshing" anything. You're the only person who
has any problems "refreshing" something. Tell me what is this
"refreshing", and why no-one else has problems with it.

TC [MVP Access]

 

[dbahooker]

refreshing linked tables?

relinking tables?

you MAKE YOUR END USERS DO IT THEN?

or let me guess; you spend 3 seconds each time you open the app; going
through and relinking tables?

IT IS ALL MUCH MORE COMPLEX THAN ANYTHING THAT COMES FROM ADP
NO LINKING NO REFRESHING
NO DSN, NO DSN-LESS

NOTHING
NONE OF THE BS

Any competent Access developer writes code to do that automatically.

shit kid; im so competent; am i really the only one that doesn't like
making my end users wait 30 seconds to open their app?
i mean MDB is a JOKE KID

what do you really think that i dont know the object model?
shit i'll take you on in a race sometime if you want.. Access is _EASY_

Access-- VBA side-- is the best programming environment ever. It is
much easier than VB6.

MDB? is the crappiest database engine ever made. I mean-- mySql is a
much much much better, faster engine for example.

I just have a problem with file-based systems; it just
a) doesn't scale
b) doesn't perform

AND IM SICK AND TIRED OF HAVING TO REBOOT FILE SERVERS BECAUSE SOME
STUPID LDB FILE WONT RELEASE

 

[dbahooker]

'everyone else knows how to use the product properly'

shit you dont USE the product
you just run around using WORKAROUND AFTER WORKAROUND since MDB is
inherently a flawed system

 

[TC]

refreshing linked tables?

relinking tables?

you MAKE YOUR END USERS DO IT THEN?

or let me guess; you spend 3 seconds each time you open the app; going
through and relinking tables?

It seems you can't even understand English!

I * W R I T E C O D E * that * D O E S I T A U T O M A T I C A
L L Y * .

As does * E V E R Y O N E E L S E * , * E X C E P T Y O U * .

HTH,
TC [MVP Access]

 

[TC]

Which does not take * A N Y * time, because the code only relinks
them when they have * M O V E D * , and the previous links * N O
L O N G E R W O R K * .

See if you can understand this, Aaaron. You really don't need to be
Albert Einstein.

TC [MVP Access]

 

[dbahooker]

i dont believe you

there isn't a line of code anywhere in the world that takes no time to
run.

you write code that makes your end users sit around and jerk off for 15
seconds every time they open their database?

in my company; you would be out of a job kid.

Access Data Projects don't do this kindof shit. grow up and lose the
training wheels.

I mean DUH

 

[dbahooker]

your strategy consumes:

a) DEVELOPMENT TIME
b) END USERS TIME
c) TESTING TIME
d) EXCESSIVE NETWORK TRAFFIC

i mean-- would this take 1 second if you had 300 tables?
if the answer is YES then you're using the wrong technology.

ADP doesn't have ANY of this crap.

and people DO have a hard time with it; i mean-- half of the posts on
this newsgroup have to do with refreshing, relinking, DSNs, linking,
importing, exporting

with SQL Server-- Access Data Projects; it is a lot easier to point in
between databases

no horsing around
but if you're in NorthwindCS.ADP

you can write a view 'Select * from TempDb.dbo.Sysobjects'

you dont have to REGISTER a new database
you dont need to WORRY about DRIVERS
you dont need to DEAL with DSNs or DSNLESS

Access Data Projects work MUCH MUCH BETTER than stupid little MDB and
you're too ingrained with obsolete tools to UNDERSTAND REALITY.

the reality is that it takes time and resources to test, develop; and
exeucte.

and my solution-- with BETTER queries-- my solution that DOESNT HAVE A
2GB LIMIT.

my solution that DOESNT HAVE TO DEAL WITH HALF OF THE SILLY WORKAROUNDS
THAT YOU DEAL WITH?

_I_CAN_OUT_DEVELOP_YOU_KID_