date not posting

[Richard Kreiss]

> -----Original Message-----
> From: Kenneth Brody [mailto:kenb at fptech.com]
> Sent: Friday, March 11, 2011 12:54 PM
> To: rkreiss at gccconsulting.net
> Cc: filepro-list at lists.celestial.com
> Subject: Re: date not posting
> 
> On 3/11/2011 12:47 PM, Richard Kreiss wrote:
> >> -----Original Message-----
> >> From: Kenneth Brody [mailto:kenb at fptech.com]
> >> Sent: Friday, March 11, 2011 12:44 PM
> >> To: rkreiss at gccconsulting.net
> >> Cc: filepro-list at lists.celestial.com
> >> Subject: Re: date not posting
> >>
> >> On 3/9/2011 3:28 PM, Richard Kreiss wrote:
> >>>> From: Kenneth Brody [mailto:kenb at fptech.com] On 3/9/2011 3:04 PM,
> >>>> Richard Kreiss wrote:
> >> [... nyd(10)=@cd reuslts in a blank field ...]
> >>>>> Anyone have a suggestion as to why in one case the field is blank
> >>>>> and in the other, the field is filled.
> >>>>
> >>>> Add the following to both processing tables, after the assignment:
> >>>>
> >>>>        mesgbox "@CD = '"&   @cd&   "'  nyd(10) = '"&   nyd(10)&   "'"
> >>>>
> >>>> What do you get in each instance?
> >>>
> >>> Will have to wait until tomorrow to check what the values are.
> >>
> >> What did you get?
> >
> > Ken,
> >
> > Changed the value to post from @cd to @td as this would be the correct
> > system date to post.
> 
> Well, if you wanted to put today's date, then that's the way to go.  But
you
> had coded it to put the creation date of the current record.
> 
> What did you get for the @CD test?
> 

Ken,

It was incorrect coding.  Being pressed to get this piece done and it had to
be used in 4 separate places with slight changes in 2 fields.

This is what happens when one is being rushed to get programming done -
simple errors in coding.

Richard