|
|
>It would be easy to over-allocate check payments ...
>Do you actually have a way of distinguishing between checks that were already
allocated...
I have a large pile of paper (registrations and copies of checks) with notes
on them! :D The goal of this project is to be able determine the allocation
with SQL. Unfortunately I am in the position of both having to do the work that
the application I am building will eventually do, *and* building the
application. The silver lining is that I think I'll build something very useful
to the person who steps in after me (who will possibly not be a web designer,
but more of an admin) because I will know what they will need to get the work
done efficiently.
It seems like, in the long run, I wouldn't need the 'Paid' field, because I
could use the 'WorkshopRegPaymentID' field to indicate payment. Until then,
though, I need to keep it because in another part of this project, I'm
displaying rosters that show 'paid' and 'completed' that involve that field.
I'm using MS SQL for the active database. I do some work with Access locally.
|
|