At 2008-09-24 10:04 +0100 Robertson, Forbes wrote:
If you have a pointer field on the record, then the script can check this value, and then call the appropriate sub-script
Forbes - thanks for your response, but I'm not sure I fully understand it. Do you mean something like:
A field in the tasks table holds a unique value. There is one script which picks up that number. In the script there is something like: if number = 1, do script "print newsletter labels" if number = 2, do script "generate renewal forms" if number = 3, do script "lapse members unpiad for this year" and so on.. I can see that would work, but it seems a bit klunky.
But on reading your first paragraph, I was thinking that you would want a join table between members and tasks? So that you would know what needs doing to who (so to speak)
I didn't actually say that the system is designed to server multiple users, but that is indeed the case. Thus there is a need to connect each task with who does it, not who it gets done to. The scripts that do the actual work figure out who to do it to (with appropriate finds etc). There is a table of users and the tasks table includes a user ID field to relate each task to the correct user.
regards Rowland -- | Wilma & Rowland Carson http://home.clara.net/rowil/ | <[EMAIL PROTECTED]> ... that's Rowland with a 'w' ...
