First, Happy New Year to all the "comp.databases.ms-access" community.

I have a technical/advice question.

For the past 8 years I've been using MS Access to solve most basic,
and sometimes quite advance, problems for my company; and so far, so
good. MS Access have been doing a Supperb job.

Now, one of the recent program that I've created, I noticed how
complex it is and how much code it requires. I'm not concerned with
the coding but with the "back end" db. See, in all my DB's I have a
mde file on the client computer with the forms, reports, etc. and the
'back end" on a NT Server (we are converting to Win2k Server soon). I
have noticed how slow the writting to the "back end" db is and
sometimes the data is not saved right.

Recently we updgrade a server and the old one (decent one) is
available for me (new toy..ha ha.. ).

I was thinking on continuing programing in MS Access but the "back
end" on a server with DB2 or Oracle (or any other for that matter). To
be honest, I have very little knowlege about both of them.

Any recommendations on which one to use? I'm looking for something
with ease of configuration and yet powerful. Something that is
compatible with Access. The little experience I had with DB2, I have
noticed that it requires a lot of commands to create a db, at least I
have notice on the installations, and have stoped me from thinking
about it. Now Iam.

I'd really appreciate any suggestions or comments you might have or
maybe, pointing me on the right direction.

Many thanks to all you.

Happy new year, man

Well, it all depends. Oracle and DB2 are powerful, but they also
require you to break open the 1000 page ref manual each has and do
quite some reading.

so, you should ask yourself:
a) do i need all of DB2/Oracle's capabilities? (if yes, go ahead and
start reading)
b) am i willing to spend 'bout a month or two reading up?
tradeoffs. my answer, would be "hell yeah!" ofcourse


George Marselis

EI User <fenixb99 (AT) hotmail (DOT) com> wrote:

The three most common performance problems in Access 2000 or newer are:
- LDB locking which a persistent recordset connection or an always open bound form
corrects (multiple users)
- sub datasheet Name property set to [Auto] should be [None]
- Track name AutoCorrect should be off

If the problem is for everyone when starting up the MDB then it likely needs a
decompile.

For more information on these, less likely causes, other tips and links to MS KB
articles visit my Access Performance FAQ page at
http://www.granite.ab.ca/access/performancefaq.htm

I'd suggest SQL Server/MSDE. Partially because MSDE is free. Mind you it is
throttled to five processes, which is *not* the same as five users. And because
MSDE/SQL Server will integrate better with Access.

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

On Sun, 02 Jan 2005 21:09:46 GMT, Tony Toews <ttoews (AT) telusplanet (DOT) net>
wrote:

Many thanks.... I'll start looking into SQL Server/MSDE....

Again, Many thanks....