Request: How to Use ODBC Bridge Windows CSV
Status: Inactive
Brought to you by:
jtellis
Menu
▾
▴
Could someone post the steps to using the ODBC bridge to link to a text file in Windows?
For example I have an ODBC Text driver named "text", set to the path were I have a csv file named "text.csv". My fields in the csv file is: EMPNAME EMCHARGE EMHOURS EMPROJ EMDATE EMLINE EMCSLT.
Its my understanding with no outside JDBC Drivers I can use the ODBC Bridge to link to that text file.
So I guess I'm asking what goes into:
Driver File:
Data Source:
Database:
Table:
Thanks, also if you are still needing someone to help with the OSX packaging I may be interested in doing that from home. I do not know Java but would be willing to try to learn. I need to learn more about Unix installation anyway.
Thanks,
iolaire
I don't think you'll be able to export to a text file... ConsultComm needs to obtain database metadata in order to show fieldnames/check data types/etc. I haven't tried it, but I'm not sure it will work. The alternate way might be to either 1) Use projects.xml in your preferences directory as the file you want or 2) Use XSLT to transform projects.xml to a text file.
If you're interested in doing OSX packaging we'd be more than happy to have ya - the first step would just be obtaining the .src.tar.gz file, OSXize, Java SDK 1.4.2 and Jakarta's Ant then trying to build ConsultComm from source. If you get that far, packaging should be a breeze!
Yes you are right, it doesn't work with text or dbf files. I set up my database in Access and it works just fine.
I'll look into the package making steps over the next few weeks and see if I can contribute.
Thanks,
iolaire
So it doesn't work with access it seems, there are various problems with mapping fields and the like. I guess I forget this at work on the PC, but I still want to work with it at home.
iolaire
Yup, Access doesn't work for the same reason text files and csv's don't work - lack of metadata support. If you want to store historical data the best bet would be to either install MySQL on the local machine (which might be overkill), keeping copies of projects.xml or using XSLT to transform the projects.xml into a format you might want to keep.
You also *might* be able to find a JDBC driver that exports to XML or CSV's instead of using JDBC-ODBC-Text. That might be your best bet.