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!
-
Congratulations Shaun E on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Export table!!!
- Thread starter midou
- Start date
You can't natively, you could export to an intermediate format that Access could import.
Alternatly, if you know you have Access installed, you could automate it. John Koziol does just that in his Fox to Access Downsizer. You can get it at the UT (
"DBC2MDB - Fox to Access Downsizer January 16, 2001 13:30 - The Upsizing Wizards in VFP help us move our data and database schema to Oracle or SQL Server. But what about "downsizing" to Access? DBC2MDB is a wizard that allows you to move your database and table structure to a new or existing MDB and, optionally, move the data itself."
Rick
Alternatly, if you know you have Access installed, you could automate it. John Koziol does just that in his Fox to Access Downsizer. You can get it at the UT (
"DBC2MDB - Fox to Access Downsizer January 16, 2001 13:30 - The Upsizing Wizards in VFP help us move our data and database schema to Oracle or SQL Server. But what about "downsizing" to Access? DBC2MDB is a wizard that allows you to move your database and table structure to a new or existing MDB and, optionally, move the data itself."
Rick
What in the world is the reason MS doesn't provide an import / export facility for Access? Is it at heart some sort of VB - VFP rivalry? I can't imagine it's technically that difficult to do. After all there are ODBC drivers to let them talk to each other.
Dave Dardinger
Dave Dardinger
- Thread starter
- #4
Hi!
Ok, I export my table easily, but now when I want add a record to the table "agent1.dbf" (it's a view),it's added but not in the table which exported by access, I wrote this code in the Init form which contain a grid :
[OPEN DATABASE BDGESTION
STORE SQLCONNECT('ges_com', 'connecter1') TO dd
SQLCONNECT()
STORE SQLCONNECT() TO dd
USE AGENT1
replace MAT_AGENT with 11
replace nom with "XXX"
SQLCOMMIT(dd)
thisform.refresh()]
Tell me please how can I correcte my code.
Many thanks.
Ok, I export my table easily, but now when I want add a record to the table "agent1.dbf" (it's a view),it's added but not in the table which exported by access, I wrote this code in the Init form which contain a grid :
[OPEN DATABASE BDGESTION
STORE SQLCONNECT('ges_com', 'connecter1') TO dd
SQLCONNECT()
STORE SQLCONNECT() TO dd
USE AGENT1
replace MAT_AGENT with 11
replace nom with "XXX"
SQLCOMMIT(dd)
thisform.refresh()]
Tell me please how can I correcte my code.
Many thanks.
Dave,
I never suggested that VFP and Access can't connect to each other's data - through ODBC and now through OLEDB. The question I read was is there an explicit EXPORT capability, and there isn't. IMPORT / EXPORT has never been a high priority especially when you attach directly to this data and programmatically "exchange" the whatever data is required. (VFP also can't EXPORT anything newer than Excel 5.0!)
Rick
I never suggested that VFP and Access can't connect to each other's data - through ODBC and now through OLEDB. The question I read was is there an explicit EXPORT capability, and there isn't. IMPORT / EXPORT has never been a high priority especially when you attach directly to this data and programmatically "exchange" the whatever data is required. (VFP also can't EXPORT anything newer than Excel 5.0!)
Rick
Well, people do need to move data from one format to another. It'd seem that 'import' and 'export' would be the natural rubrics under which to do so. I hope you didn't think I was implying that I thought you couldn't transfer the data. Indeed, I've done the Access to VFP shuffle myself as well as to and from SQL Server, Excel and pipe delimited and comma delimited files. But it's a whole lot less confusing and prone to error if you say 'Export to Access' and be done with it. It's bad enough that MicroSoft often doesn't provide ways to get at the data of other companies, since there might be legal problems. But there's no excuse for not being able to provide direct transfers to their own products.
Sure you can set up ODBC connections and then port the data across, but it's round about and wastes time. It still sounds like office politics to me.
Dave Dardinger
Sure you can set up ODBC connections and then port the data across, but it's round about and wastes time. It still sounds like office politics to me.
Dave Dardinger
Dave,
I think that if there is an "excuse" for the VFP team NOT dealing with Import/Export on many file types, is the constant changing each new version requires. I believe Access alone has had 7 different formats in the last ~9 years! (As opposed to .DBF files - two formats in 20+ years.) Those formats that are supported don't change. Ultimately, would you rather have the Fox team adding each new version of the Office file formats, or adding developer UI and functional improvements? After all there is a limited budget for updates, not to mention those that are always complaining about "bloat" of the Fox .EXE and runtime files.
The real hope now is XML - a promising "universal" data exchange format.
Rick
I think that if there is an "excuse" for the VFP team NOT dealing with Import/Export on many file types, is the constant changing each new version requires. I believe Access alone has had 7 different formats in the last ~9 years! (As opposed to .DBF files - two formats in 20+ years.) Those formats that are supported don't change. Ultimately, would you rather have the Fox team adding each new version of the Office file formats, or adding developer UI and functional improvements? After all there is a limited budget for updates, not to mention those that are always complaining about "bloat" of the Fox .EXE and runtime files.
The real hope now is XML - a promising "universal" data exchange format.
Rick
Well, that's a point. I'm trying to educate myself on XML for a project I may be doing soon. Actually I'm going to do the project for my own education anyway, but if I can work it out with the other fellow it may have commercial possibilities. From what I understand I'll probably have to upgrade to VFP 7 to do much work with XML.
Anyway, I'll probably have a lot of questions as it goes along. In fact I think I'll start another thread on one subject of interest.
Dave Dardinger
Anyway, I'll probably have a lot of questions as it goes along. In fact I think I'll start another thread on one subject of interest.
Dave Dardinger
- Status
Similar threads
- Locked
- Question
