Recurring Events

[Vincent]

I am working on a database project that supports reoccurring
events very similar to those seen in Microsoft Outlook. I was doing
some research on the best way to do this and came across Allen
Browne's sample database (http://allenbrowne.com/AppRecur.html). I am
wowed by the simplicity and elegance of Allen's approach. However, I
need to support more flexible recurrence, such as a job taking place
on the last day of the month. Is anyone familiar with Allen's sample
database? If so, do they have any ideas on how this type of
recurrence could be implemented without totally screwing up Allen's
elegant approach? Thanks.

Vincent

[Allen Browne]

Not sure there's a simple answer to your question, Vincent.

As the article states, it's really an example of how to approach it. How to
extend it will depend what else you need to achieve.

With regard to your specific example perhaps you could add an Offset field
(type Number.) You could then have a recurring event for the first of the
month, minus 1.

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Vincent" <an**********@verizon.netwrote in message
news:05**********************************@i76g2000 hsf.googlegroups.com...

I am working on a database project that supports reoccurring
events very similar to those seen in Microsoft Outlook. I was doing
some research on the best way to do this and came across Allen
Browne's sample database (http://allenbrowne.com/AppRecur.html). I am
wowed by the simplicity and elegance of Allen's approach. However, I
need to support more flexible recurrence, such as a job taking place
on the last day of the month. Is anyone familiar with Allen's sample
database? If so, do they have any ideas on how this type of
recurrence could be implemented without totally screwing up Allen's
elegant approach? Thanks.

Vincent

[Vincent]

On Oct 19, 10:52*am, "Allen Browne" <[e-mail]>
wrote:

Not sure there's a simple answer to your question, Vincent.

As the article states, it's really an example of how to approach it. How to
extend it will depend what else you need to achieve.

With regard to your specific example perhaps you could add an Offset field
(type Number.) You could then have a recurring event for the first of the
month, minus 1.

--
Allen Browne - Microsoft MVP. *Perth, Western Australia
Tips for Access users -http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Vincent" <[e-mail] in message

news:05**********************************@i76g2000 hsf.googlegroups.com...

* * I am working on a database project that supports reoccurring
events very similar to those seen in Microsoft Outlook. *I was doing
some research on the best way to do this and came across Allen
Browne's sample database (http://allenbrowne.com/AppRecur.html). *I am
wowed by the simplicity and elegance of Allen's approach. *However, I
need to support more flexible recurrence, such as a job taking place
on the last day of the month. *Is anyone familiar with Allen's sample
database? *If so, do they have any ideas on how this type of
recurrence could be implemented without totally screwing up Allen's
elegant approach? *Thanks.

Vincent

Allen,

I have found a solution, of sorts, to the above issue. Now I am
dealing with an issue of scale. For example, in the application I am
utilizing this in, it would not be uncommon for a customer to have
over 1000 revolving service records in the database. If I have 1000
records in the "tblCount" table, and all of the revolving service is
infinite (no recurrence count specified), then the cartesian query
will generate 1,000,000 (1,000 * 1,000) or more records. Is there a
good way to limit the number of records that are generated by this
query (short of reducing the number of records in the "tblCount"
table)? Again, I'm not sure if there is a good answer.... Thanks.

Vincent

[Allen Browne]

The cartesian will generate a million records for the example you give. It
may still run in only a few seconds: try it.

You might need a temporary table if you want to do lots of further
processing of the results.

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Vincent" <an**********@verizon.netwrote in message
news:dd**********************************@e38g2000 prn.googlegroups.com...
On Oct 19, 10:52 am, "Allen Browne" <[e-mail]>
wrote:

Not sure there's a simple answer to your question, Vincent.

As the article states, it's really an example of how to approach it. How
to
extend it will depend what else you need to achieve.

With regard to your specific example perhaps you could add an Offset field
(type Number.) You could then have a recurring event for the first of the
month, minus 1.

"Vincent" <[e-mail] in message

news:05**********************************@i76g2000 hsf.googlegroups.com...

I am working on a database project that supports reoccurring
events very similar to those seen in Microsoft Outlook. I was doing
some research on the best way to do this and came across Allen
Browne's sample database (http://allenbrowne.com/AppRecur.html). I am
wowed by the simplicity and elegance of Allen's approach. However, I
need to support more flexible recurrence, such as a job taking place
on the last day of the month. Is anyone familiar with Allen's sample
database? If so, do they have any ideas on how this type of
recurrence could be implemented without totally screwing up Allen's
elegant approach? Thanks.

Vincent

Allen,

I have found a solution, of sorts, to the above issue. Now I am
dealing with an issue of scale. For example, in the application I am
utilizing this in, it would not be uncommon for a customer to have
over 1000 revolving service records in the database. If I have 1000
records in the "tblCount" table, and all of the revolving service is
infinite (no recurrence count specified), then the cartesian query
will generate 1,000,000 (1,000 * 1,000) or more records. Is there a
good way to limit the number of records that are generated by this
query (short of reducing the number of records in the "tblCount"
table)? Again, I'm not sure if there is a good answer.... Thanks.

Vincent

[Vincent]

On Oct 31, 10:04*pm, "Allen Browne" <[e-mail]>
wrote:

The cartesian will generate a million records for the example you give. It
may still run in only a few seconds: try it.

You might need a temporary table if you want to do lots of further
processing of the results.

--
Allen Browne - Microsoft MVP. *Perth, Western Australia
Tips for Access users -http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Vincent" <[e-mail] in message

news:dd**********************************@e38g2000 prn.googlegroups.com...
On Oct 19, 10:52 am, "Allen Browne" <[e-mail]>
wrote:

Not sure there's a simple answer to your question, Vincent.

As the article states, it's really an example of how to approach it. How
to
extend it will depend what else you need to achieve.

With regard to your specific example perhaps you could add an Offset field
(type Number.) You could then have a recurring event for the first of the
month, minus 1.

"Vincent" <[e-mail] in message

news:05**********************************@i76g2000 hsf.googlegroups.com....

I am working on a database project that supports reoccurring
events very similar to those seen in Microsoft Outlook. I was doing
some research on the best way to do this and came across Allen
Browne's sample database (http://allenbrowne.com/AppRecur.html). I am
wowed by the simplicity and elegance of Allen's approach. However, I
need to support more flexible recurrence, such as a job taking place
on the last day of the month. Is anyone familiar with Allen's sample
database? If so, do they have any ideas on how this type of
recurrence could be implemented without totally screwing up Allen's
elegant approach? Thanks.

Vincent

Allen,

* * *I have found a solution, of sorts, to the above issue. *Now I am
dealing with an issue of scale. *For example, in the application I am
utilizing this in, it would not be uncommon for a customer to have
over 1000 revolving service records in the database. *If I have 1000
records in the "tblCount" table, and all of the revolving service is
infinite (no recurrence count specified), then the cartesian query
will generate 1,000,000 (1,000 * 1,000) or more records. *Is there a
good way to limit the number of records that are generated by this
query (short of reducing the number of records in the "tblCount"
table)? *Again, I'm not sure if there is a good answer.... *Thanks.

Vincent

Ok, I'll try running it. Thanks again for coming up with a great
solution to doing recurrence!

Vincent