PDA

View Full Version : ODBC Exporting Error



hand471037
2004-05-04, 10:38 PM
Hey all,

I've been doing some work with making complex Excel Spreadsheets to parse the ODBC export out of Revit for cost models. And I've hit a snag. Everything was working great, but now when I try to export to an existing ODBC database via the Excel file driver, I keep getting error message '22' from the driver.

Any clue what's going on?

Thanks a ton!

gregcashen
2004-05-04, 11:00 PM
From the Revit help file:


AutodeskĀ® RevitĀ® has tested the following ODBC drivers:

Microsoft Access
Microsoft Excel
ODBC Exports to Excel create one table per worksheet.
You can export to an Excel file only once. Multiple exports to Excel are not supported.
Microsoft SQL Server
Microsoft Text Driver: Not supported by Autodesk Revit.
Autodesk Revit may be able to interface with other ODBC drivers, depending on the features supported by the driver. Contact Autodesk Revit Client Support for assistance.

...so I think what you are trying to do (export multiple times to the same excel spreadsheet) won't work...

hand471037
2004-05-04, 11:44 PM
aw ****! :(

But I think I can figure out a way to make this work.... grrrr....

Thanks for the tip Greg!

GuyR
2004-05-05, 12:11 AM
Jeffrey,

Can you post the complete error message? Trying to export twice to a XLS should give you this message:

[code:1:c746286ef4][HY000] [Microsoft][ODBC Excel Driver] Deleting data in a linked table is not supported by this ISAM. (-5410)[/code:1:c746286ef4]

Which is an ODBC error message as per
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcodbc_error_codes.asp

Greg's right, using Excel is really only good for a once off export unless you manipulate, extract data from a MDB from within excel (using VB).

ODBC is not a database, just a way of talking to the database. In this case excel is the database. To take data from any project into your special spreadsheet you need to either export to a temp.xls file and then merge in differences or create an access database (MDB) and extract the data from this.

For doing what you want to do a simple API that allowed you to PULL data from a project would be the ideal :-)

Guy

hand471037
2004-05-05, 12:14 AM
is it possible to dump ODBC data from Revit to Access multipule times?

gregcashen
2004-05-05, 12:17 AM
is it possible to dump ODBC data from Revit to Access multipule times?

Yes. It should also be possible to do the excel multiple linking thing using Ken Stowe's script...however that works!?!

GuyR
2004-05-05, 12:20 AM
Jefffrey


is it possible to dump ODBC data from Revit to Access multipule times?

Yes, and you can dump multiple projects to the same database if you want. There are some issues with doing this and it's not my preferred method. I prefer one database/project.

Guy

Marek Brandstatter
2004-05-05, 01:01 PM
It should also be possible to do the excel multiple linking thing using Ken Stowe's script...however that works!?!

Ken Stowe's journal script automates the batch export of multiple schedules from a single project file to multiple deliminated txt files. These txt files can be then be linked to a "master" Excel file, that parses them and repopulates itself. Without the script you would have to individually export each schedule.

If your skills lie with Excel this is probably the best way to go as you don't need to interact with the entire ODBC database - just the schedule data you require.

If you're confortable with Access or SQL, AND you've familiarized yourself with Revit's ODBC tables - then ODBC Export to Access as this is a one-step process. With each export, Revit repopulates the ODBC table information to correspond to the project.

hand471037
2004-05-05, 03:47 PM
If you're confortable with Access or SQL, AND you've familiarized yourself with Revit's ODBC tables - then ODBC Export to Access as this is a one-step process. With each export, Revit repopulates the ODBC table information to correspond to the project.

This is more along the lines of what I working on. I want to make an automatic thing based off of ODBC, vs. the Scripting export. Thanks for all the help!