Adding data into a Table via a Switchboard

[johnp79]

I was wondering if it was possible to do this, currently if I need to add a new record, I have to add it all in the tables section, this works fine but would be easier if it could be done through the switchoard somehow.

 

[Kassy]

Automatic addition of data

On a similar line I also have data I would like to add to a table or make a table but rather than have a form in which you have to fill in the data is it possible to update the table via the system date? e.g I have a membership database where the season starts in September for 1 year and up until now it hasn't been used properly by the club so information is sketchy. I would like to be able to start the table now and automatically update the table every year when the new seaon starts on 01/09 by having a field that increments the Season (2005-06), so next September when members rejoin the season will automatically be 2006-07 and so on building up a seasons table. Or would it be better to just create the table up to say -year 2020 and just fill in the bits. Not sure how to go about this.

 

[Kassy]

Roster Table

I presently have a member table with usual data, containing a field for first join(this is inherited) but the 'users' of the DB have just put in when a members re-registers so consequently some members have first date registration but others show 'present date join' not 'first date join'! So 2 different confusing pieces of data are produced. I want to eliminate this and have left the 'first join' date(dont know if its really needed unless for history purposes?) but have a table of payments(again Inherited)which is a subform and when a member joins the 'payment date' acts as the 'join/renew date'. I would like to produce some reports to let the club know if members are new/old/lapsed, compare seasons etc. However I thought by introducing a seasons table/field it might eliminate this confusion so that members can be identified with the seasons they paid for. It's at this point I can't work out if I'm supposed to just run a query to get this information or add another table. What you suggest sounds like my payment table which contains PayID,PayType,PayAmount,PayDate and (Lapsed?Tick box I havent yet decided if it's necessary so have not implemented it ) Now....... should I have another table like you suggest and if so my 'payment table' will need altering? or just add extra fields to payment table. How to change this mess to achieve a sensible 'good practise' solution Im not sure!