How do I web enable an Access application

J

JamesX

Hallo

I've written an application using MS Access 2003 and want to make it
available to users online. I note that access forms and reports can be
converted to data access pages but any underlying code in these objects is
lost and does not convert.

Please tell me that I don't have to rewrite the application in HTML or other
such language. Can anyone point me in the right direction as to how best to
convert an access application to a fully web enabled application.

Any help is much appreciated.
 
R

Rick Brandt

JamesX said:
Hallo

I've written an application using MS Access 2003 and want to make it
available to users online. I note that access forms and reports can be
converted to data access pages but any underlying code in these
objects is lost and does not convert.

Please tell me that I don't have to rewrite the application in HTML
or other such language. Can anyone point me in the right direction as
to how best to convert an access application to a fully web enabled
application.

Any help is much appreciated.

You have to rewrite the application in HTML or other such language.
(sorry)

Think about it. Have you ever seen a web page that looked like an Acess form?
If it was easy to convert Access apps to web pages don't you think you'd see a
LOT of such pages given how easy Access is to build apps with?
 
A

Albert D. Kallal

Data access pages are quite much uselessness, as the end users have
to have the correct version of office installed. For internal company
networks
they are useful, but for a "public" web site, they are of no use.
Please tell me that I don't have to rewrite the application in HTML or
other
such language.

Yes, you do. You can't cut wood with a hammer. You have to use the right
tool for the right job.

do you expect to using auto-cad, or ms-access to draw drafting diagrams?

If you write your application as web based, and want to turn it into a
desktop application, then again you have to re-write the whole appcation.
Can anyone point me in the right direction as to how best to
convert an access application to a fully web enabled application.

You asking how to turn a airplane into a car. It not going to happen.

Ms-access is not a web based tool, has no relation to web based systems, and
you simply have to re-write the application.

So, what direction? Well, you have a GAZILLION choices here. The asp.net
tools is likely a good choice for you. Often, it depends on what kinds of
web servers your company has. In other words, what kind of web servers is
your company running now, and what tools and web software are they running?.
I mean, when you write web based systems, you have to write that software to
the "system" that your web server is running.

I don't if a developer can come into your company, and say we are going to
use FoxPro in place of ms-access on a simple whim of the day. You would have
to change all of your ms-access applications to FoxPro because one person
wants to use FoxPro.

So, just like the code for ms-access has to be written because you using
ms-access, that code you write in ms-access will not work in FoxPro. The
exact same reasoning apples to web based systems. Likely your first
question(s) should be to your IT support department, and you need to ask
them what software are they using for the web servers. You can't just go off
and learn some web based system, but then wake up to find out your company
is not running that type of web system. If you don't have a web server, then
you have to talk to your web hosting company and ask them what tools and
software they support (The asking of what software system they are using is
*EXACTLY* the same as finding out a company is using FoxPro and not
ms-access for their desktop software.

So, when you find out what tools your web server supports, then:

a) ether you lean the tools and software your web hosting company is
using
or
b) you change providers to one that uses the same web tools you
(eventually) have chosen.

If you company has some web based software now, then obviously, you might
not have the clout or ability to make then change to any web based set of
tools, and thus will have to learn/use what they have now. If your company
does not have a web site, then you can much choose whatever tools you want,
and then find a hosting company that can run that software (or, your company
can setup their own web servers, but security issues are VERY serious, as
then your company network is exposed to the web, and if you don't know
*EXACTLY* what you are doing, then your whole company can be exposed to the
web).

Anyway, not a lot more advice can be given here because this is the wrong
newsgroup, wrong tools, and access has nothing related to web based systems,
and is the wrong technology.
 
A

aaron.kempf

Rick

don't be a smart ass
Microsoft _JUST_ promised us this functionality-- to be able to open
an Access form in Visual Studio-- did they deliver? NO

DAP is a wonderful tool

if you MVPs weren't a bunch of cry babies then maybe it would be more
popular


basically, re: OP

you need to do this

a) move to SQL Server (MDB is not allowed for web servers)
b) use Access Data Projects to keep your existing application
available
c) ADP also allows VPN Wireless, WAN and LAN usage. MDB this doesn't
wor
d) use DreamWeaver-- it has some wonderful wizards- to build a web UI

hope that helps

I'd really stay away from the MS web development world.
MS doesn't 'get' the internet or web development

if they did they would support PHP
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top