Re: Communication between Web and Windows application

From: Jochen Neyens (jneyens_at_analyz-it.be)
Date: 08/07/04 

Date: Sat, 7 Aug 2004 13:01:09 +0200

Using the same database for the client and web application will not be
possible since the client application is from another software vendor. The
Web APP has to push data to this practice management application by
inserting it directly to the backend .MDB file. There will be no concurrency
issues since there will be max 2 connections to the local MDB: 1. The
practice management app itself en 2. the web application. We'll be using SQL
server as backend for the web application.

"Ryan Riddell" <RyanRiddell@discussions.microsoft.com> wrote in message
news:29A1D7ED-08E8-4BB3-8665-D2E499381A26@microsoft.com...
> Just use the same database for the client and web applications. If you
have
> 1500 users though, be warned that Access won't allow more then 10 (I think
> it's 10) concurrent users, so be careful with the connections. If you are
> using something more robust for the web app, then use that for the client
app
> as well.
>
> "Jochen Neyens" wrote:
>
> > We're in the process of developing an e-commerce application that vets
can
> > use to order medicines. One of the requirements is that the web
application
> > can communicate with a locally installed practice management application
> > that uses MS-Access as a backend database. This way shipped e-commerce
> > orders can we imported in the practice management application to update
the
> > stock levels of medicines.
> >
> >
> >
> > The web-application will be written in ASP.NET / C#.
> >
> >
> >
> > My question:
> >
> >
> >
> > Which technology should we use to communicate from within the browser
with
> > the MS-Access backend of the practice management application? I was
thinking
> > of writing an ActiveX control using C# and let this sign by Verisign.
Will
> > this be a good solution? Is there an alternative solution? The interface
> > will be used by approx 1500 clients. An important aspect is the ability
to
> > deploy code via the Internet. The current order application is written
in VB
> > 5 and needs to be installed from a CD-Rom which is a nightmare for code
> > updates. This has to be replaced with an ASP.NET application whilst
> > maintaining the ability the synchronise data with the locally installed
> > practice management application.
> >
> >
> >

Quantcast