Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

Register Log in
  • Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Search results for query: *

  1. daveb77

    Unexplained truncation with str function when used in a 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...
  2. daveb77

    Unexplained truncation with str function when used in a query

    @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.
  3. daveb77

    Unexplained truncation with str function when used in a query

    @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...
  4. daveb77

    Unexplained truncation with str function when used in a query

    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...

Part and Inventory Search

Back
Top