F
Fred Boer
Hello!
Not a question, just a comment; and if I can't talk about Access with all of
you, well, then who *will* listen to me?
Today I was trying to make a small modification to the "Check Out" form I
have in my school library application. I've always thought the process I was
using was pretty darn clever. It used 3 forms and a number of procedures.
Well, I was just staring at it and it suddenly hit me that I could replace
all of this with a single unbound form and one continuous subform. I also
realized I could replace a bunch of code with one SQL INSERT statement.
Now, I'm not saying I'm clever (if I were would it have taken me two years
to see this?), but time and time again, I seem to find that there is a
simpler way to do things than the way I imagined it needed to be done. It's
almost as if there should be a rule printed above my monitor: "IF IT IS
COMPLICATED - IT IS WRONG!". In fact, I think that's just what I'm going to
do!
Thanks for listening!
Cheers!
Fred Boer
Not a question, just a comment; and if I can't talk about Access with all of
you, well, then who *will* listen to me?

Today I was trying to make a small modification to the "Check Out" form I
have in my school library application. I've always thought the process I was
using was pretty darn clever. It used 3 forms and a number of procedures.
Well, I was just staring at it and it suddenly hit me that I could replace
all of this with a single unbound form and one continuous subform. I also
realized I could replace a bunch of code with one SQL INSERT statement.
Now, I'm not saying I'm clever (if I were would it have taken me two years
to see this?), but time and time again, I seem to find that there is a
simpler way to do things than the way I imagined it needed to be done. It's
almost as if there should be a rule printed above my monitor: "IF IT IS
COMPLICATED - IT IS WRONG!". In fact, I think that's just what I'm going to
do!

Thanks for listening!
Cheers!
Fred Boer