In my opinion, Web Database access is one of the best reasons for corporate intranets. There are a bunch of different methods, each with its own advantages and disadvantages.
|
|
-
The standard, solid approach: I've written cgi-bin scripts in Perl, C, and even Visual Basic using the corresponding built-in database libs (sybperl, oraperl or VB). -
Java's JDBC to ODBC bridge works a little differently. The Java applet downloaded to the client machine can directly connect to the DB. This is exactly the same as standard client server except that the application (the applet) is downloaded each time. The easy download provides simple version control, feature addition, a means to nimbly respond to user's changing requirements without a lengthy, complex install process. Unfortunately, the bridge is not too stable. Supposedly, the pure Java JDBC drivers are much better.
-
New "API-level" tools such as Netscape's LiveWire. Livewire supports very fast response from databases (as it was meant to). In addition, JavaScript was easy to develop with. Relatively immature, Livewire is sometimes a little quirky. -
The Oracle Web server is another.
| WEB DATABASE ACCESS LINKS |