 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
MS Access Forum / Importing / Linking / July 2005Importing data from Foxpro (DOS) to Access 2003
Hello, Can anyone tell me how I can import data from an old DOS Foxpro system into Access 2003? The Foxpro system is still in use, so its data is changing and this won't be a one-time import. Thanks! James This will link your Foxpro table. DoCmd.TransferDatabase acLink, "dBase III", strFoxProPath, _ & acTable, "wdmaster", "wdmaster" Then construct a query to append the data from the linked table to your Access table. Then use a DeleteObject to remove the link to the FoxPro table > Hello, > [quoted text clipped - 5 lines] > > James Hi, Thanks for the response. I've tried implementing this but I'm getting an odd error. For strFoxProPath I've put "c:\fox\fn125.dbf", but when I execute it I get: -------------------- Run-time error '3044': 'c:\fox\fn125.dbf' is not a valid path. Make sure that the path name is spelled correctly and that you are connected to the server on which the file resides. -------------------- However, there definitely IS a file c:\fox\fn125.dbf and drive C is certainly accessible. My actual line is: DoCmd.TransferDatabase acLink, "dBase III", "c:\fox\fn125.dbf", acTable Any suggestions? Thanks! James > This will link your Foxpro table. > DoCmd.TransferDatabase acLink, "dBase III", strFoxProPath, _ [quoted text clipped - 14 lines] >> >> James I don't know if this will fix it, but you are missing the table name. It will be the name you want the mdb table to be. DoCmd.TransferDatabase acLink, "dBase III", "c:\fox\fn125.dbf", acTable, "YourTableName" > Hi, > [quoted text clipped - 44 lines] > >> > >> James Hi again, Sorry to keep bothering you with this, but I've tried the modification you suggested and still get the same error. My code is: DoCmd.TransferDatabase acLink, "dBase III", "c:\fox\fn125.dbf", acTable, "tblStock" and when I execute it I get: -------------------- Run-time error '3044': 'c:\fox\fn125.dbf' is not a valid path. Make sure that the path name is spelled correctly and that you are connected to the server on which the file resides. -------------------- Any other suggestions would really be appreciated. James >I don't know if this will fix it, but you are missing the table name. It > will be the name you want the mdb table to be. [quoted text clipped - 53 lines] >> >> >> >> James Hi James, What is your exact statement? A path should be like "C:\Fox\" and not include a table name. Set Path To C:\Fox\ Use TableName  SignatureCindy Winegarden MCSD, Microsoft Visual Foxpro MVP cindy_winegarden@msn.com www.cindywinegarden.com Blog: http://spaces.msn.com/members/cindywinegarden > I've tried implementing this but I'm getting an odd error. For > strFoxProPath I've put "c:\fox\fn125.dbf", but when I execute it I get: [quoted text clipped - 40 lines] >>> >>> James Hi Cindy, As you've probably seen with my reply to Klatuu, my exact statement is: DoCmd.TransferDatabase acLink, "dBase III", "c:\fox\fn125.dbf", acTable, "tblStock" Although I've also tried: DoCmd.TransferDatabase acLink, "dBase III", "c:\fox\fn125.dbf", acTable and: DoCmd.TransferDatabase acLink, "dBase III", "c:\fox\fn125.dbf", acTable, , "tblStock" They all yield a run-time error 3044 telling me that my path is invalid. If we assume that the Foxpro file is c:\fox\fn125.dbf can you tell me exactly what line(s) of code to use to import it into Access? Thanks! James >> -------------------- >> [quoted text clipped - 5 lines] >> >> -------------------- > Hi James, > [quoted text clipped - 48 lines] >>>> >>>> James DoCmd.TransferDatabase acLink, "dBASE III", "c:\fox", _ acTable, "fn125", "fn125.DBF" |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.