Implementing an Access application via web

[Guest]

I have seen a number of questions and looked at articles involved with
showing an Access table in a web page.

I am planning to build an application involving input forms, menus, and
reports.

My question is this: Is it reasonably efficient to first build the
application as a non-web application and then convert it to a web
application, or would there be so much rework as to make it better to start
it as a web application? Reason is I am not too familiar with ASPs and IIS
and just concentrating on getting an app running first I think would be
easier for me.

Thanks,

John

 

[Pat Hartman\(MVP\)]

There is nothing transferable from an Access application to a web based
application except the data. That means that building the application with
Access first is a waste of time. However, it will probably point out the
weakness of web applications.
Why do you need a web application? If you don't have to open the
application up to people outside your company, you will probably be happier
with a desktop client/server application.

 

[Guest]

Thanks very much for the response. This is a eye-opener. I had assumed that
there was some type of SaveAs within Access that would create an ASP or at
least building blocks for an ASP. Also interesting to hear of the weakness
of a web-based application with Access data. I realize the web interface is
not as feature-rich as a client interface, but I had assumed that it had been
worked to minimize the web shortfalls.

It is for internal use, and I can go with a traditional client application.
Just thought the web would be more convenient for use in cases where Access
is not installed. However, with the traditional client application I can
always use NetMeeting or remote desktop to access another machine.

Thanks again,

John

 

[Pat Hartman\(MVP\)]

I've been building applications for over 30 years and to my mind web
applications are a giant step into the past. They are very much like the
CICS applications that I used to develop in the 70s and 80s except that
they're prettier. Access (actually Jet) can be used as the be for a web fe
but it can't handle anything but very light traffic. The only advantage
that web applications have over client/server applications is that they
don't need to be distributed and installed on individual PCs to work. So as
long as you have control over who uses the application, a client/server
application will provide a richer experience.

 

[Guest]

Good advice. I will go the non-web route, then later experiment to see the
trade-offs.