[AccessD] Access data to and from Website

MartyConnelly martyconnelly at shaw.ca
Thu Dec 1 15:12:39 CST 2005


Are you going to do this from a corporate web server with IIS or use a 
web hosting service?

Then you have to make a choice ASP, ASP.Net or WSS (Sharepoint)
If you haven't used before the times frames to do a basic hookup, as an 
uneducted guess
1 week, 2-3 weeks, 1 month
Then it depends on what equipment and software you have available, Web 
Hosting  starts at $20 a month

If I needed a basic site up on web hosting that allows Access mdbs,
I would use genericdb and ASP. It would take only a couple of days.
But it would be hopless for security unless you understand and code for 
things like
SQL injection attacks.
There are some commercial products that will do this
Frontpage or
I would use this product to get up and running in a day or two with web 
hosting service
cost $99
http://www.access2asp.com/download.htm
Then you are left with the big problem of updating your corporate mdb 
from the web hosted one.
How soon do you need the data?

 
Mailing lists and sites on ASP

http://aspadvice.com/default.aspx
http://www.aspfriends.com/aspfriendshome/
http://www.asp.net/

You might want to use a dotnet portal for a corporate intranet
like DotNetNuke open source

http://www.dotnetnuke.com/

As starting projects for getting a basic standard understanding
For ASP genericDB recommended by Nature magazine
Series of ASP wizards to create a config page to get at mdb files
Site appears down today
http://www.genericdb.com

http://www.erobillard.com/default.aspx

For ASP.Net a bit dated but Web Matrix
http://asp.net/webmatrix/


If you have the cash and looking to the future you might want to use
Sharepoint Portal to house your mdb tables

This is the guy Eli Robillard who wrote GenericDB 6 years ago.

http://weblogs.asp.net/erobillard/articles/SharePointResources.aspx

Borge Hansen wrote:

>Hi all,
>I have no experience with pushing data between an Access database and a Website.
>
>We have a full featured event management database that we have been running for
>some years - still in Access97 about to be moved to A2003...
>
>A number of conferences are held throughout the year.
>An organization registers one or more attendees
>An attendee is assigned to several sessions throughout the conference.
>
>All registration related communication used to be handled with postal mailout,
>now most is done via email.
>
>However, de peple in de top office is reguesting that an attendee should be able
>to visit the website (currently just a static web page) - view all sessions for
>the conference and select which ones they wish to attend, and submit this
>information.
>Relevant procedures will then integrate the information captured into the event
>database.
>
>Something needs to be up and running rather quickly.
>
>I'd appreciate anyone's comments, suggestions for a simple, quick and efficient
>solution.
>
>What tools to use?
>Estimated time involved?
>Code samples
>
>This is how I envisage the functionality:
>
>The Attendee enters LastName, FirstName, City and emailaddress.
>Entry is validated against table containing data for all attendees for the
>Conference: AttendeeID, LastName, FirstName and City (we may not have email
>address at this stage). As part of the validation the AttendeeID is identified.
>
>The list of sessions are displayed grouped by Date and Session Category and
>order by StartTime.
>There is a tickbox (?) for each Session where the Attendee can tick if he/she
>wishes to attendee the Session. Each session is identified by a SessionID, (not
>necessarily displayed).
>
>At the bottom a Submit button.
>
>Curious as to how do you make this part of the webpage dynamic/interactive -
>i.e. the code behind the submit button to walk the page, identify the sessions
>that have been ticked and capture the corresponding SessionID
>
>
>
>The submit button will do the following:
>1. Send an email confirming Name, City and listing the Sessions that the
>Attendee wishes to attend.
>
>2. Capture information from the Webpage to a table called say
>tblWebRegistrationAttendee
>AttendeeID
>emailaddress
>
>(no editing of Name and City information)
>
>and to a table called say
>tblWebRegistrationAttendeeSession
>AttendeeID
>SessionID
>
>The captured information will then be copied from the webserver tables to the
>event database for further processing.....
>
>.... that's it
>any suggestions, comments, pointers appreciated
>
>regards
>/borge
>
>
>
>  
>

-- 
Marty Connelly
Victoria, B.C.
Canada






More information about the AccessD mailing list