Change MS Access Database to Internet Site

  • Thread starter Thread starter dan2bhm
  • Start date Start date
D

dan2bhm

I know this is VERY general question and don't expect someone to list ever
step for me. I'm looking for some suggestions on which steps to take. Let me
explain my Database first...

Multiple Tables (some are actually linked as a SharePoint List)
Multiple Queries (select, append, update, delete...etc all sorts of essential
queries)
Multiple Forms (all have VB code which perform different tasks when the user
clicks a "button")
Multiple Modules (performing all sorts of automation: Linking to Excel,
PowerPoint, Word, Outlook)

The Database was designed to perform a variety of "behind the scene"
functions so that it could be used by the lowest technically proficient
people. So maintaining a clean and professional GUI is of the utmost
importance. Additionally, I don't want to lose the thousands of lines of VB
in th process. I realize that transforming this into a different platform
will create a LOT of work to reestablish the overall operation/functionality
that it currently provides.

What I need is suggestions on useful articles or step by step suggestions to
put this beast on the internet.

Meaning, should I create a SQL server to hold the tables, queries, modules.
Then use HTML to create new "forms" and link everything back together? What
about .NET? I don't know much about the .NET technology, but I'm a quick
learner and would LOVE to develop skills with that language.

I sincerely appreciate any guidance that you GURUs can provide. All
suggestions are welcome.
 
If by "to Internet Site" you mean you want to access data through the
Internet with a browser, then, most part of your Access application is most
like useless. You need a web application. Maybe, you can still use the data
portion (tables, or some of the queries) as a web application's data store,
but forms, reports, VBA code in the access application will not be used at
all.

Basically, you need to re-develop your on-line version of the app, using web
technology (ASP, ASP.NET, Java, PHP, Perl... of your choice). If you do, you
may want to seriusly look into a database server (SQL Server, MySQL...),
unless you realy know the Jet database can handle the web traffic and meet
the security requirement.
 
most importantly; don't use MDB for anything in the real world ever.

use MSDE or SQL Server, even SQL Express.

or shit, Oracle Express, DB2, mySql-- anything except MDB anywhere
 
Back
Top