Search results for query: *

Thanks to Olaf & JRB-Bldr, and the others that replied. @Olaf This is exactly what happened: <In a first step VFP determines which field type it needs for expressions like STR(field,4,1) and while that seems straight forward to create a C(4), vfp may fail on a null value and create a C(1) field...

@TamorGranor Thanks for your reply. I tried PADL, PADR and even PADC to no avail. I used the equal sign as my pad character and the query returned a left aligned = sign for the column interrogated.

@jrbbldr Thanks for your reply <So I am guessing that your real query string is something else.> Yes, this was a test query to isolate the problem. <This doesn't make much sense since all the values for mon will be 12.0 and mon1 will be '12.0' or else no records will be returned if nothing...

I'm using the VFP 6.0 command line to interrogate some free tables. There is a field called MON defined as a numeric (width 4, decimal 1) which I've been attempting to export to Access. There are issues with a straightforward pull via the VFP OBDC driver so I've been attempting to get around it...