I thought that's what you were referring to, but wasn't sure. I almost felt
bad for being impatient with him. Problems like this intrigue me and I was
interested to get to its source, but I didn't want to have to work harder
than he did to resolve his problem.
I wanted to write back to say he could call the module anything he wants.
Module names are the single most irrelevant thing in Microsoft Access. Go
ahead, name your modules basMurderNMayhem or WhatTheHeck_functions.
I suppose it would be wrong to name them Tables, Forms or Reports, but
the compiler will warn you if you attempted such a foolish thing.
So, I know what the module name is, but not the procedure. He might as
well given me other extraneous and useless information, such as the time
the module was created, the color of shirt he was wearing at the time
and the dog's last cholesterol reading.
It doesn't seem like that long ago that I was asking simple questions at
this newsgroup. As a rule, no one is chastised for being dumb. If so, I'd
have abandoned this group out of shame years ago. However, if you want
to get answers to complicated questions, you're going to have to cooperate
and communicate clearly.
I didn't take offense at the shouting, but I don't deny Lyle's right to be.
As for me, I just prefer to pursue conversations that are easy to follow
with those who work hard on their communication skills.
--
Danny J. Lesandrini
dl*********@hotmail.com http://amazecreations.com/datafast
"Lyle Fairfield" <ly***********@aim.com> wrote ...
Well, perhaps I have misinterpreted this exchange and more than perhaps
I should have just left the whole thing to Danny,