I want to do the same thing and have similiar questions.
From the replies here, I would conclude that all the code in the forms and
controls on the forms, including combo boxes and formats , would be
non-portable.
I'm just starting to develop on the web and I noticed that some web-hosting
services provide a windows platform. Check out:
http://www.ipowerweb.net/products/windowshosting/index.html
They talk about ODBC support for access databases. I'm not sure what that
means and how an access db can be used on the web, it being a desktop
database.
As I mentioned. I'm just starting this myself and still have a lot to learn.
Is anybody here using an access db as a backend on a web server?
Rix said:
Hello Guys,
We are in development of building our software as a VBA Module in MSAccess.
We would like to have a Web Version of our software using the programming we
have now (800 pages) based off of MSAccess and VBA, (I guess?)
I need to know what it take to create a web interface that interacts with
our software?
Basically I would like to create a web verison of my software.
Also can I create an API for other software companies to connect to?
I have a company who uses Java or Netbeans, I can't remember and they want
to connect to our software and pull information from it.
He says we have to convert it to VB.Net or something else to be able to
create an API they can talk to. Is there not a way to do it with VBA and
MSAccess?
Thanks for all your help.
Converting the code to VB.NET could potentially solve both problems. You
could call functions in a VB.NET class library from an ASP.NET web page. I
don't know whether you can do that directly from a Java app, but if you
can't do it directly, you could do it via an ASP.NET Web Service.
How difficult it will be to convert the code depends, of course, on the
actual code to be converted. If it uses mostly members of the VBA object
library, it might not be very difficult to convert. If it relies heavily on
members of the Access object library, it will probably be more difficult to
convert.
--
Brendan Reynolds
Access MVP
I need to know what it take to create a web interface that interacts with
our software?
Ms-access is not a web based tool, and has nothing to do with the web.
So, your development tools, your code are of no use for the web.
He says we have to convert it to VB.Net or something else to be able to
create an API they can talk to.
Yes, if you are creating a auto-cad system, you use auto-cad software. IF
you are creating a web based system, you use software designed for the web.
Is there not a way to do it with VBA and
MSAccess?
No, not really, it is no more of a tool for d3 graphical designs, then
asp.net is for the web....
you have to use the right tool for the right job...
--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
(e-mail address removed)
Converting to .Net would bring it into the year 2006, but the conversion can
be a bear. It would be much easier to port your code into VB6 and publish it
as a dll or ActiveX control. I would imagine/hope that Java could interop
with a dll.
Unfortunately, it sounds like you are at one of those tough decision points.
However, the longer you wait to upgrade everything to .Net, the harder it
will be to maintain and to convert later.
Barry
