Revit Architecture

Reply
Distinguished Contributor
tomislav.zigo
Posts: 197
Registered: ‎04-20-2005
Message 1 of 6 (753 Views)

DB Link and ODBC Export differences

753 Views, 5 Replies
05-06-2011 01:56 PM

Can someone explain why is there a difference between DB link and ODBC Export. Both exporters are omitting several different tables, and the available fields. For example ODBC will export Mass Element Surfaces but it will not include Categories table and Shared parameters in project information table, while DB Link cannot see Mass Surface types.

In order to see the entire database one needs to export twice, through ODBC and via DB link.

I would say that this is a bit inconvenient.

*Expert Elite*
ccollins
Posts: 866
Registered: ‎09-28-2009
Message 2 of 6 (750 Views)

Re: DB Link and ODBC Export differences

05-06-2011 02:06 PM in reply to: tomislav.zigo

I'm not sure why there are such differences.

 

But I had a thought........

 

What if you exported to 3D dwfx and imported into Adesk QTO--would you see the Mass surfaces and the parameters?

 

 

Cliff B. Collins
Registered Architect/BIM Manager
Thalden Boyd Emery Architects
St. Louis, MO
Distinguished Contributor
tomislav.zigo
Posts: 197
Registered: ‎04-20-2005
Message 3 of 6 (724 Views)

Re: DB Link and ODBC Export differences

05-08-2011 11:19 AM in reply to: ccollins

That might work, but it does not offer the flexibility of cross-referencing data from multiple sources within the familiar environment like SQL server.

 

Distinguished Contributor
tomislav.zigo
Posts: 197
Registered: ‎04-20-2005
Message 4 of 6 (713 Views)

Re: DB Link and ODBC Export differences

05-09-2011 06:15 AM in reply to: ccollins

DWF doesn't carry mass element associated surface information that is necessary for the rapid take off.

Active Contributor
GlynnisP
Posts: 36
Registered: ‎01-08-2009
Message 5 of 6 (695 Views)

Re: DB Link and ODBC Export differences

05-11-2011 06:45 PM in reply to: tomislav.zigo

I'm also not sure how to explain the differences between those two tools.  I can only say, that as a software developer, we too have struggled to make sure all the various parameters are exposed for our tool, and in many cases it's been unearthed only after a specific request has been made.  In other words, it's not all neatly organized in some list, waiting for us to published (though I wish it was).

 

Here's a screenshot of how we expose the parameters related to Masses.  I'd be curious to know if even this would meet your needs?  Fields in grey would be editable (in Excel).

 

Regards,

Glynnis Patterson, Architect

www.ideatebimlink.com | www.ideateexplorer.com

 

 

Distinguished Contributor
tomislav.zigo
Posts: 197
Registered: ‎04-20-2005
Message 6 of 6 (683 Views)

Re: DB Link and ODBC Export differences

05-12-2011 09:34 AM in reply to: GlynnisP

Glynnis,

 

Linking properties is not an issue, whether done through custom API or using SQL and Forms to work with a database. What, concerns me is the inconsistency between two tools that are created for bridging the gap between an object database and relational one.

For my purpose I am getting what I need, but it would be much nicer to do this in a consistent way.

 

Regards,

 

Tomislav

Post to the Community

Have questions about Autodesk products? Ask the community.

New Post
Announcements
Are You Going To Be @ AU 2014? Feel free to drop by our AU topic post and share your plans, plug a class that you're teaching, or simply check out who else from the community might be in attendance. Ohh and don't forgot to stop by the Autodesk Help | Learn | Collaborate booths in the Exhibit Hall and meet our community team if you get a chance!