I am thinking of what type of back-end to use for this. I suppose the simplest case would be a delimited text file of the form
user1,service1,date1,pass user1,service2,date2,pass user1,service3,date3,fail user2,service1,date4,pass ...that's quite simple and easy. the only drawback is the repetition of the username for each of his services.
an alternative would be XML, but that seems like overkill, and frankly I am not too comfortable with it, though I used it for a similar application before, more as a learning exercise than anything else.
Thoughts?
TIA, T.
In reply to Re: A web-based checklist in the manner of the checklists in the bathrooms of fast-food restaurants
by OfficeLinebacker
in thread A web-based checklist in the manner of the checklists in the bathrooms of fast-food restaurants
by OfficeLinebacker
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |