Very Computer

>I am involved in developing an application that uses a
>central database on a web server to store its data. The
>application should run on the client side and access the
>database across an Intranet.

>We have not decided the programming language to use but
>it will probably be either Java or VisualC++. We will have
>SQL server 6.5 running on an NT server with IIS.

>The application must be able to query the database, process the
>results and display appropriate information. So using HTML and
>ASP does not seem to do the job.

>>I am involved in developing an application that uses a
>>central database on a web server to store its data. The
>>application should run on the client side and access the
>>database across an Intranet.

>>We have not decided the programming language to use but
>>it will probably be either Java or VisualC++. We will have
>>SQL server 6.5 running on an NT server with IIS.

>>The application must be able to query the database, process the
>>results and display appropriate information. So using HTML and
>>ASP does not seem to do the job.

>If I may ask, why wouldn't ASP work?  It's suited nicely for
>this type of thing, especially in an IIS/MTS environment.

>> I would like to avoid using HTML
>>anyway if possible.
>>What other options are there to connect to the web database and
>>what programming language would be best suited?

>If you're going to access the database via a web server, some
>HTML is going to be involved, even if it's just the tags
>to display an applet.

>A lot depends on how you really want to architect your application
>and what it needs to do.  If possible, I tend to have all
>my processing done on the server(s) and rendering the presentation
>layer in HTML.  This gives me maximum front end portability
>and the freedom to not only use any language (Java, C++, VB,
>even Perl) on the server.  I tend to use Java, since my code
>can be used via CORBA, RMI, or DCOM, as well as implemented
>as a JavaBean or ActiveX component.  The key is not "picking
>a programming language," it's determining an application
>architecture, and then picking languages to implement each
>piece of the application - use the appropriate language wherever
>you need it.

>If your app is more than just data entry and retrieval, you
>may consider writing a Java applet for your presentation layer.

>>>I am involved in developing an application that uses a
>>>central database on a web server to store its data. The
>>>application should run on the client side and access the
>>>database across an Intranet.

>>If your app is more than just data entry and retrieval, you
>>may consider writing a Java applet for your presentation layer.

> I am involved in developing an application that uses a
> central database on a web server to store its data. The
> application should run on the client side and access the
> database across an Intranet.

> We have not decided the programming language to use but
> it will probably be either Java or VisualC++. We will have
> SQL server 6.5 running on an NT server with IIS.

> The application must be able to query the database, process the
> results and display appropriate information. So using HTML and
> ASP does not seem to do the job. I would like to avoid using HTML
> anyway if possible.
> What other options are there to connect to the web database and
> what programming language would be best suited?

> We are just in the specification phase of the project and
> before I jump into the deep end I would like to know if anyone
> has any experience for this type of application.
> Any hints appreciated.

> cheers
> holger
> --

> I don't think I made my intentions perfectly clear. What I want to
> do is write a fat-client that does more than data entry and retrieval.
> For this reason something like ASP does not do enough since for example
> the application must be able to use, manipulate and process data
> retrieved from the database. I really need the client app to do some
> processing of the data.

> >>>I am involved in developing an application that uses a
> >>>central database on a web server to store its data. The
> >>>application should run on the client side and access the
> >>>database across an Intranet.

> >>If your app is more than just data entry and retrieval, you
> >>may consider writing a Java applet for your presentation layer.

> I don't think I made my intentions perfectly clear. What I want to
> do is write a fat-client that does more than data entry and retrieval.
> For this reason something like ASP does not do enough since for example
> the application must be able to use, manipulate and process data
> retrieved from the database. I really need the client app to do some
> processing of the data.

> Is RMIJdbc-JDBC-ODBC the best way to go? Are there other options?

> What is the performance like with Java for serious applications?

> I am new to Internet programming so forgive my ignorance.

> Thanks!

> cheers
> holger
> --