Data driven sites often brings people crashing back to earth at an alarming rate. Desiging and implementing your database is more important than writing the site itself. A bad database design will be unwieldly and make it difficult if not impossible to effectively pull information out and get information into it.
Now, before I go off on one with a long-winded explanation of the ins and outs, it would help to know a couple of things first:
1. Which version of FrontPage are you using ?
2. Since you will need some dynamic content which is likely to involve an Access database and ASP pages or at the very least a CSV file, what exactly does the web host support that the site will be published to ?
3. Do you have any experience at all in database design ?
4. When you say a membership system, is this to have log-in forms and parts of the site for members only or is it merely to keep track of a club member list or similar ?
The good news is that there are several free to use membership systems available that you could port to your project but without knowing what it is you actually want to do and what sort of information you want to process it's impossible to give an off the peg solution. Do you want a forum area, a chat system, log-in and log-out, member only areas of the site and so on or...
As much detail as you can supply would help one of us to point you in the right direction.