Re: Ms Access and Java Servlets-Applet

[Galbreath, Mark]

Title: RE: Ms Access and Java Servlets-Applet

You are correct; I did not mean to imply that ANSI SQL would not work with Access.  But Access was designed to be a simple desktop database, not an enterprise datasource.  Nevertheless, I've run into many companies who use it as such, and then scratch their heads when it blows up.

-----Original Message-----
From: Steve Glasser [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, September 11, 2002 7:58 AM
To: [EMAIL PROTECTED]
Subject: Re: Ms Access and Java Servlets-Applet

You can use ANSI-92 SQL with MS Access without a problem. Access like other databases (ie. Oracle, mySQL) has proprietary features that are not part of the ANSI specification. Just stay away from those and you will be fine.

I would agree that Access and ODBC-JDBC is not a preferred configuration for production, but I have a client that we have used Access on a moderately busy web site for a three years now without a problem. I would prefer something else, but it's tough to convince them when it works.

Steve

-----Original Message-----
From: Galbreath, Mark [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, September 11, 2002 6:46 AM
To: [EMAIL PROTECTED]
Subject: Re: Ms Access and Java Servlets-Applet

And Access uses a proprietary (imagine that) form of SQL that is supported
only by Microsoft ODBC-JDBC drivers (imagine that).  And Milt is correct,
the bridge drivers are not recommended for production use.

Mark

-----Original Message-----
From: Milt Epstein [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, September 10, 2002 9:02 PM
To: [EMAIL PROTECTED]
Subject: Re: Ms Access and Java Servlets-Applet

On Wed, 11 Sep 2002, RUTHERFURD, Michael wrote:

> > I'm not an MS person, but pretty much all I've heard about using
> > Access with servlets can be summed up in one word: Don't.  (Yes, a
> > contraction counts as one word! :-)
> >
> > Milt Epstein
>
> Milt, were any reasons given (technical, not evil empire)? I'm
> interested as I'm currently having to simulate the prod DB in ms
> access (the prod db will be a funky teradata box but they haven't
> got the hardware yet).

Yes, the reasons were technical (e.g. things didn't work well, both
because of Access and the JDBC-ODBC bridge -- which I believe isn't
recommended for production use).  I don't really recall details, but
that's what the archives are there for, no?

Milt Epstein
Research Programmer
Integration and Software Engineering (ISE)
Campus Information Technologies and Educational Services (CITES)
University of Illinois at Urbana-Champaign (UIUC)
[EMAIL PROTECTED]

___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".

Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html

___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".

Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html