Access On the Web - HELP!!!!

[fatmcgav]

Hi There,

I have a problem and i need some help.
I have recently started a project at school to design a membership database for a small golf-course, which contains all the info about all the clubs members; name, address, tele#, mem type, join date, ccard #, etc. The database was originally meant to be running on a single computer in their reception.
But now, i feel that i could take it one step further, and possibly try and market the project, by expanding the membership section of the website i designed, so that members can access the database online, and be able to change their membership details, pay bills etc, and also, major point, be able to book tee-reservation times.
Right, so thats the scenario, now onto the database.

The members database at the moment contains three tables, one containing the main membership info: mem#, name, mem type, join date, exp date. Tbl 2 contains the members contact details, and table three contains their payment details: membership value, amount payed, amount to pay, etc.

If i want to expand it to be able to book tee-off times, the members will need to access a members section on the website, login, access the tee-reservation page, and search and select tee-reservation times upto 6 months in the future.

What i am not sure of is:

• What back-end to use - whether to leave it as MsAccess, and link using PHP, or convert the MsAccess BE to MySql, and link all the tables.
• How to make the table so that it will display dates up-to six months in advance, whilst clearing any dates that are in the past, but still storing all the past tee-off times reservations in a member table, so that the golf club can find out how many times x memeber has used the club etc.

I know that sounds a bit long winded, and i'm sure i'll find some other features that i need to add, and that i'll need help for, but thats all that i need for now.

Thanks for all replies in advance.

Regards
FatMcGav

 

[Hammy]

.

 

[Hammy]

MySQL is definately the db of choice for PHP. If you wish to use Access, consider using ASP or ASP.NET instead....this has the advatage of the language being similar to what you would use in an Access procedure.

You can connect to an Access db with PHP, but it requires an ODBC entry to be setup (as far as I know, PHP is not my language of choice).

To answer your second question, you could create an "archive" table in your db to store all past tee times. This way, they are not in the current table, but are still available. To move them over, you could go one of two routes.

1. When the user submits a query to view their tee times, you could run a secondary queries to append all old records to the archive table, then remove them from the current table. Not the preferred method, as it creates more overhead and slows the user experience.

2. In your back-end db admin (which you will HAVE to build), have a section where a staff member, can click a button and it will perform the append/delete of old records.

To view tee times up to six months in advance, you simply take care of this in your SQL statements...only choose records that in within now and now+6months, and only allow records to be entered that are less than now+6months.

Everything is done with web forms, and you have to manually create all your queries within you ASP/PHP code.

Hope this helps,
Hammy

 

[fatmcgav]

ASP :S

Ah, ASP, i spose i never really thought about using ASP. Might look into using it.
Anybody know of any Personal Web Development Servers that allow you to run ASP.Net, preferabily free ones, not the expensive M$ ones.

Thanks.

Also, is there a wayy of automating the process of copying out old records, say, once a week, so that it is one less job for the user.

Thanks Again.

 

[Hammy]

IIS and the .net framework are both free downloads from MicroSoft. Download / Install them, you now have a personal development server capable of ASP, ASP.Net.

I don't know if there is a task schedule capability in ASP/ASP.net or not.....I am more of a CF guy myself.

[edit]Tutorial Here for scheduling a task with ASP.NET[/edit]

Hammy