<html><body><div style="color:#000; background-color:#fff; font-family:times new roman, new york, times, serif;font-size:12pt"><div><span></span> </div><div><span>Problem number 1 solved. For future reference for anyone doing low level import of MSSQL dates, their format is yyyy-mm-dd.</span></div><div><span>A simple set of mid strings solved the problem. Dates now work.</span></div><div><span></span> </div><div><span>Problem 2 is still out there. It is called a <span style='font-family: "Times New Roman","serif"; font-size: 12pt; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA;'>'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.</span></span></div><div><span><span style='font-family: "Times New
Roman","serif"; font-size: 12pt; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA;'></span></span> </div><div><span><span style='font-family: "Times New Roman","serif"; font-size: 12pt; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA;'>Help,</span></span></div><div><span><span style='font-family: "Times New Roman","serif"; font-size: 12pt; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA;'></span></span> </div><div><span><span style='font-family: "Times New Roman","serif"; font-size: 12pt; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language:
AR-SA;'>Rick Hane</span></span></div><div><span><span style='font-family: "Times New Roman","serif"; font-size: 12pt; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA;'></span></span> </div><div><br></div> <div style="font-family: times new roman, new york, times, serif; font-size: 12pt;"> <div style="font-family: times new roman, new york, times, serif; font-size: 12pt;"> <div dir="ltr"> ----- Forwarded Message -----<br> <font size="2" face="Arial"> <b><span style="font-weight: bold;">From:</span></b> Richard Hane <yoresoft@sbcglobal.net><br> <b><span style="font-weight: bold;">To:</span></b> fplist <filepro-list@lists.celestial.com> <br><b><span style="font-weight: bold;">Cc:</span></b> Rick Hane <rhane@deluxestitcher.com> <br> <b><span style="font-weight: bold;">Sent:</span></b> Wednesday, May 8, 2013 10:11 AM<br> <b><span
style="font-weight: bold;">Subject:</span></b> two problems when importing MSSQL to filePro<br> </font> </div> <div class="y_msg_container"><br>
Hopefully, there are others our there who have imported data from MSSQL to filePro odbc.<br> <br>If you remember I posted a couple of the fpodbc processes I wrote to import data from our ERP system (written in MSSQL). This has now grown to over 15 processes that run each night as a scheduled task.<br> <br>Today I have found a couple of problems that I need help on.<br> <br>1. I do not seem to be able to get a date mm/dd/yyyy to come over. It leaves the field blank. Problem may be that the varaible I use is set to 10,mdyy/. I don't recall the MSSQL date format to try and work around this problem.<br> <br>2. This one is a little harder. I am importing our Bill of Materials (BOM) file. No problem with any of the data except in the qty used field. From what I can see by looking at the raw SQL data, the factors I have a problem with would look like 6.2499999999999 E-2. If the
factor is .0624999999999 with out the E-2 then no problem. It appears the E-2 means move the decimal left two places. When you do an odbc import in to Excel the value are correct. Obviously Excel knows how to handle this. Do we have anything that can handle this.<br> <br>One other small problem. When testing a process I sometimes have to run it twice as the first time processing says it can not make the ODBC connection. Start it again and all is fine. I see no reason why.<br> <br>Thank you in advance<br>Rick Hane<br>Controller<br>Deluxe Stitcher Company Inc<br>ISP Stitching Products<br>http://www.deluxestitcher.com/<br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: http://mailman.celestial.com/pipermail/filepro-list/attachments/20130508/b8a850db/attachment.html <br>_______________________________________________<br>Filepro-list mailing list<br><a
href="mailto:Filepro-list@lists.celestial.com" ymailto="mailto:Filepro-list@lists.celestial.com">Filepro-list@lists.celestial.com</a><br>Subscribe/Unsubscribe/Subscription Changes<br>http://mailman.celestial.com/mailman/listinfo/filepro-list<br><br><br></div> </div> </div> </div></body></html>