Recording Information using Calendar

gls

Want to be guru
Local time
Tomorrow, 03:17
Joined
Mar 5, 2008
Messages
40
Hi

Have been working on my DB for some weeks and I'm now at the stage where I'm having a few difficulties that I feel might require code. I'm happy with what I have put together and have been learning lots along the way. Can some assist with these issues,

Have a table called tblAccess_Issues
Have a table called tblInput
Have form called frmAccess_Issue
Have a frm called frmInput_Box
Have a form called frmCalendar

The table tblAccess_Issues records the issue of a tenant not allowing access to a property. Records tenant name and property address and a few dates.

The form to enter these details into tblAccess_Issues is called frmAccess_Details. I have a button on frmAccess_Details that will load frmCalendar if clicked with the mouse. The calendar loads OK. If I click on a date, the frmInput_Box will appear so I can type data into a particular date using frmInput_Box. The information entered into that particular date is recorded in tblInput, so the date recorded and the comments written all go into tblInput. So far this is working fine.

My problem is, one tenant may have many comments written about the access issue to the property. Lets say we have 10 comments on different dates all relating to that one property & tenant. What I need the tblInput table to do is record the 10 comments against the one record in tblAccess_Issues. I don't know how to do this. The tblAccess_Issues uses has a jobID as the key and that is set to autonumber. I also have a unique identifier being the property reference number, a number that we use to identify a particular property. Any ideas on how to link the 10 or so comments to the one record in tblAccess_Issues.

Also, a quick one that you will probaablt know, I would like to remove all the drop down menus, file, edit, insert etc in the DB and only leave one custom menu availble to users. Can you assist. I can post the DB if you need it.

Help appreciated and I hope I have made sense.

Garry
 
Simple Software Solutions

In a nutshell;

You will need to create a child table linked to the property table via the PK.
The child table will need to collect the PropertyID and also have a commentID so when you run a query you can run it via property key and see all comments for 1 property:vis

TblProperty:
PropertyId :1
PropertyName:1 Every Street

TblComments
PropertyID :1
CommentID: 1
CommentDesc Door Locked
CommentDate 01/01/2008
PropertyID :1
CommentID: 2

CommentDesc Door still Locked
CommentDate: 02/01/2008
PropertyID 1
CommentID: 3

CommentDesc Door Unlocked
CommentDate: 03/01/2008

So in summary you have what is called a one to many relationship - one property can have many comments.

CodeMaster::cool:
 

Users who are viewing this thread

Back
Top Bottom