here came the <g> tag - boy was I waiting for it ! :-)
"damorgan" <damorgan_at_exesolutions.com> wrote in message
news:3CA8CFD4.1ED6B046_at_exesolutions.com...
> I agree with everything you say. But I didn't say I thought Access was an
RDBMS
> ... only that the original correspondent did. <g> I think it is a blivet.
>
> Daniel Morgan
>
>
>
> Alan wrote:
>
> > I agree with everything you wrote, except that Access is NOT a
relational
> > database product, in the strictest sense. It does not separate the data
> > layer from the application layer (all stored in an .mdb file), which is
a
> > requirement for an RDBMS. Access is a product that gives access (NPI) to
> > data, and by the way, happens to have a place to store the data as well.
> > Lotus Approach is much better at it. At the very least, it keeps the
data
> > and application layers separate.
> >
> > "damorgan" <damorgan_at_exesolutions.com> wrote in message
> > news:3CA88D33.6F23FB6B_at_exesolutions.com...
> > > Based on what you have written you seem to be under the mistaken
> > impression that
> > > Oracle is a relational database product, Access is a relational
database
> > > product. And you can just learn a few new commands and some syntax
> > differences
> > > and be productive.
> > >
> > > Unless your job description includes "Make a huge mess" that couldn't
be
> > farther
> > > from the truth. I would anticipate that your company is about to make
a
> > huge
> > > gory mistake ... and then undoubtedly leave you and others blaming
Oracle
> > for
> > > making a bad product.
> > >
> > > I strongly urge you to tell your management that they are making a
> > horrible
> > > mistake if they do not hire the following three positions, perhaps as
> > > contractors, for at least one year. (1) UNIX sys admin with no less
than
> > three
> > > years of experience working with Oracle databases, (2) A very good
Oracle
> > DBA
> > > with experience managing multiple production instances, and (3) a
senior
> > Oracle
> > > developer who also has experience working as a DBA.
> > >
> > > And please do not use Access as the front-end to your application.
That is
> > a
> > > wonderful way to create something that is not secure, not stable, not
> > scalable,
> > > and will perform very poorly.
> > >
> > > Daniel Morgan
> > >
> > >
> > >
> > > Anderson O'Reilly wrote:
> > >
> > > > We are switching to Oracle (UNIX) from MS Access soon. Forms can be
made
> > > > easily with MS Access. How to make forms to be used with Oracle? Is
> > there
> > > > any helpful book that you could recommend? I learned how to CREATE
TABLE
> > and
> > > > INSERT INTO. Is there any convenient way to insert records without
> > typing
> > > > INSERT INTO for every record? Thanks in advance.
> > >
>
Received on Mon Apr 01 2002 - 15:38:14 CST
