two problems when importing MSSQL to filePro
Jeff Harrison
jeffaharrison at yahoo.com
Wed May 8 13:44:27 PDT 2013
________________________________
> From: Richard Hane <yoresoft at sbcglobal.net>
>To: fplist <filepro-list at lists.celestial.com>
>Sent: Wednesday, May 8, 2013 3:34 PM
>Subject: Fw: two problems when importing MSSQL to filePro
>
>
>
>Problem number 1 solved. For future reference for anyone doing low level import of MSSQL dates, their format is yyyy-mm-dd.
>A simple set of mid strings solved the problem. Dates now work.
>
>Problem 2 is still out there. It is called a 'Scientific Notation'. Only about 3% of the 18,000 BOMs have this problem. If I could ID them I could do a work around. The problem is how to do this.
>
>Help,
>
>Rick Hane
Unless I am missing something you should be able to ID these in filepro by using the contains (co) operator. So for example if field #1 had this data in it:
If: 1 co "E-"
Then: -- grab the number after the "E-" (call it X) and perform the appropriate calculation using 10 to that power.
Jeff Harrison
jeffaharrison at yahoo.com
Author of JHExport and JHImport
More information about the Filepro-list
mailing list