point well taken! i've often wondered myself if i should go back to the long
form. i may.
On Sun, Jun 1, 2008 at 3:01 PM, Gary Templeman <[EMAIL PROTECTED]>
wrote:
> Just remember that if you ever share your information with others, the
> format least likely to lead to errors is when places are
I do the same thing. My locations (both long and short) look like this:
Chicago, Cook Co., IL
The solution involves editing the geostatecodes.txt, geocountycodes.txt and
geocountrycodes.txt files. It's not too difficult to do. If you don't want
to mess with them, send me an email. I'd be happy t
Please! Give it a rest! Have you stopped to listen to yourselves? You remind
me of my 2 small children during a trip across country. When will we be
there? Are we there yet? "Billy got more ice cream than I did". I wish I
could buy comic books and crayons for all of you. Maybe that would divert
you
i have been having the same trouble with mail-archive.com over the past day
or two..
On Tue, May 27, 2008 at 7:30 PM, Steve Ayres <[EMAIL PROTECTED]> wrote:
> Ron, I just gave Dick's URL a try and got the same response "403
> Forbidden" and I'm using a Windows PC running XP. Could be just the
ue ([EMAIL PROTECTED]) wrote:
> Some possibilities:
> 1) make source comments italics as you enter/update each (highlight all,
> then CTRL & I)
> 2) start all comments with the word Comments:
>
>
> ----- Original Message -
> From: "Deck and Margot"
> To:
&g
Hi everyone,
When printing source "comments" on a report, it prints immediately after
source "text". That is all well and good, except there is no formatting
in the report that distinguishes the difference between the two. The
source "comments" begin as another regular sentence after the last
6 matches
Mail list logo
