count the no. of record on a particular date and time

[Deepak Kumar]

pls help me in a function:

i have some record on a particular day field and time field, such as- on 8/11/2011 2:00am.

Suppose on this date and time, i have 4 appointments . Now how would i count the no of record on this date & time with the help of function.. every appointment has a id.

Please reply soon.

[LaRetta]

Create another occurrence of your table (duplicate it in the graph). Maybe call it 'Same Appt'. Create a summary field called sCountAppts, which is count of any field never empty, such as your AppointmentID. Join as:

Appointments::Date = Same Appt::Date

and

Appoints::Time = Same Appt::Time

Place the sCountAppts field from Same Appt directly on your Appointments layout.

Now, why do you want to count them? If you need to search for > 1 for instance, you cannot search the summary field. You would instead need to create a calculation in your parent table which brings us to the question of why you need to know. If it is to find double bookings, you might consider stopping them before they happen. If this is a one-time thing, our response would be different than if this was an on-going need. One-time things, we would probably loop. On-going need, we might suggest a more permanent build.

Purpose for the need? :^)

[LaRetta]

I just thought of something ... are appointments only one second each? If not then what if someone has appointment on Friday at 10:00 AM and someone else has appointment on Friday at 10:15 AM or 10:10 AM? Might you not want to consider a range instead of exact-time join? Otherwise, no two appointments will match to the exact second.

struck out typo

[Deepak Kumar]

I just thought of something ... are appointments only one second each? If not then what if someone has appointment on Friday at 10:00 AM and someone else has appointment on Friday at 10:15 AM or 10:10 AM? Might you not want to consider a range instead of exact-time join? Otherwise, no two appointments will match to the exact second.

struck out typo

Create another occurrence of your table (duplicate it in the graph). Maybe call it 'Same Appt'. Create a summary field called sCountAppts, which is count of any field never empty, such as your AppointmentID. Join as:

Appointments::Date = Same Appt::Date

and

Appoints::Time = Same Appt::Time

Place the sCountAppts field from Same Appt directly on your Appointments layout.

Now, why do you want to count them? If you need to search for > 1 for instance, you cannot search the summary field. You would instead need to create a calculation in your parent table which brings us to the question of why you need to know. If it is to find double bookings, you might consider stopping them before they happen. If this is a one-time thing, our response would be different than if this was an on-going need. One-time things, we would probably loop. On-going need, we might suggest a more permanent build.

Purpose for the need? :^)

Create another occurrence of your table (duplicate it in the graph). Maybe call it 'Same Appt'. Create a summary field called sCountAppts, which is count of any field never empty, such as your AppointmentID. Join as:

Appointments::Date = Same Appt::Date

and

Appoints::Time = Same Appt::Time

Place the sCountAppts field from Same Appt directly on your Appointments layout.

Now, why do you want to count them? If you need to search for > 1 for instance, you cannot search the summary field. You would instead need to create a calculation in your parent table which brings us to the question of why you need to know. If it is to find double bookings, you might consider stopping them before they happen. If this is a one-time thing, our response would be different than if this was an on-going need. One-time things, we would probably loop. On-going need, we might suggest a more permanent build.

Purpose for the need? :^)

Thanks friend...it worked....