Let's see it,, Mark Oliva
MOliva@rjgordon.com



>FoxPro for Windows 2.6 (IBM platform)
>
>We download credit card files (TYPE SDF) every two weeks. In those files, the dates are "010101" (with the year in 2 digits, which we
>convert to FPW character format of "01/01/01"). We then create an "output" file that we send to our mainframe and it is an TEXT file (TYPE SDF) also.
>
>Once upon a time (few months ago), I was asked that if we can have more than one sets (lets call it "bi-weekly set" of data) at the same time, because the program we have now will take ALL of the data and create the output file, regardless if there is two or three sets at the same time. I did and it worked fine, but later then it appears there is a bug. We stopped do this, and I am supposed to analyst it and fix it. I have not done this for a while (other things to do...).
>
>We have an running program that work fine ALL THE WAY THROUGH. I am now doing an strip-down of VISA only and narrow down to this. I am asked to have this "bi-weekly set" working again.
>
>Now, since the dates are in text format, I had to use CTOD(billdate) type kind of thing. What I do is HARDCODE a date, namely, 1/9/99 (yes, I want to start with this "future" date for us to understand better).
>1/9/99 is Saturday. Our credit card cycle STARTS on Saturday (morning)
>and ENDS on Friday (evening) business hours (2 weeks cycle).
>
>I did was to DO CASE...ENDCASE to catch the "today's" date (memvar in
>date format, via {01/01/01} type kind of thing) to work around to get
>the "starting" date and then add 14 to get the "following 2 weeks", it
>keeps adding until it get "today's" date = or >, then subtract 14 (or
>21) and then lastly, do all kinds of IF...ENDIF, DO WHILE...ENDDO,
>etc... jumping all over, since we are expected that we will not be late, no later than 2 weeks, so I give a three or four weeks to play coding.
>
>Well, now, I like to ask anyone (seriously) if I can email this section of coding that I created and see if this would be something "good" AND maybe locate a bug AND if by possible, if this would be a Y2K as well, since one of the starting date is Dec, 23, 1999 and ending date is Jan. 7, 2000, so there is an cross-over there... I want to post the coding here, but it is 3 1/2 pages long and I don't want to offend someone. If it is ok to post it here, let me know and/or you like me to email you the section of code, please ask. Yes, this is for FPW 2.6 (I am set to go to VFP 6.0 training in Chicago in March 1999). and this is an priority that we must keep using FPW 2.6 at this time. My supervisor want to change it to VFP 6.0, but the timing is not possible at this time.
>
>Thank you and please let me know.
>
>Chuck