"ljubo lecic via AccessMonster.com" <fo***@AccessMonster.com> wrote in
message news:49******************************@AccessMonste r.com...
I am an experienced ORACLE software developer who
met ACCESS few months ago and I must say that ,so far,
I am delighted. I rapidly developed a few aplications
and everything is working extremly good.
Now, I am offered to develop something more complex.
And It must be done in ACCESS.I feel so comfortable in
ACCESS programming that I am about to accept the offer.But before my final
response I URGENTLY need some
advices and opinions from expirienced ACCESS programmers:
My questions are:
1.What are the constraints of ACCESS comparing to
traditional SQL- databases.
2.Why isn't ACCESS regarded as an SQL database(or
I am wrong)
3.Can ACCESS be used as a server database in a multi-user
environment
4.Could someone give me an example( possible situation)
when ACCESS must be replaced with ORACLE or SQL- server
5.Could I use ACCESS as software development tool to
the ORACLE or SQL-server database
Thanks in advance
--
Message posted via http://www.accessmonster.com
1. Maximum database size of 2Gb. Not scalable: depending on what the
database and it's users are doing, it will run out of steam at somewhere
between 5 and 20 users. Lacks resilience (network, client or user stupidity
problems can all corrupt the database). Useless security (as complex as it
is to set up, Access security is very, very easy to break). Strictly
speaking, these are all issues with the default Jet database engine rather
than Access as a whole, and they can all be resolved by using SQL Server or
Oracle or somesuch as the database engine instead.
2. What's an SQL database? Who cares? The question is, is Access
adequate for your job? If so, then use it: there's nothing better. If not,
then look elsewhere. Don't listen to prejudices or meaningless definitions.
3. Access can certainly be used in a multi-user environment, but the
default Jet database engine is NOT a server, which is why it suffers from
the issues described in (1) above. If you use a server database engine
instead (e.g. SQL Server), then it will be, erm, a server!
4. Oracle and SQL Server are NOT potential replacements for Access: they
are potential replacements for the Jet database engine. Access functions
very well as a client to servers such as Oracle and SQL Server.
5. Yes. With SQL Server you could build an Access ADP (newish
technology, very controversial, see many previous discussions, some folks
think they are awful, others think they are fine). With SQL Server or
Oracle, you can use ODBC linked tables (well established technique, works
very well).