|
At 10:02 23.10.2002 -0600, you wrote:
> From: "Anton Gombkötö" <gombkoetoe@ASSOFT.COM> > Sometimes things ARE NOT what they look like... ;-) Anton, Your explanation clarified much.
At least one thing i finished successfully today... ;-)
My understanding is that one file holds a list of available news letters, and another file indicates which news letters each person has subscribed to.
Exactly.
The HTML form is used to add / remove records from the subscription file based on the before / after setting of the subscription flag on the form.
Yes. The before and the current value are compared, if not equal (= CHANGED), then the newsletter:user record is either created or deleted.
It's really a perfect example of an procedure that begs for a "read next change" operation on a subfile.
That's why i posted the link... ;-)
Your code reflects a very effective
Thanks, it's rather limited; but only one user accesses his data at a time, so it's not a big concern.
(although verbose) workaround.
verbose? Do you mean much code for the task? HTML or the rest? But it's (almost) all code necessary, there's no other program necessary, one could optimize it a bit further, and the "just subscribed" and "just unsubscribed" is a toy one could remove. In my personal calculation lines vs. effect it's not so bad. But i'm open for opinions. best regards / Mit freundlichen Grüssen Anton Gombkötö Avenum Technologie GmbH http://www.avenum.com
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
