TdaTable properties

rbuser

What's the difference between the Alias, RawTableName, SQLAlias, and
TableAlias properties?

Thanks,

Ed Vander Hoek

digitalmetaphors

DADE has a lot of internal implementation details to support the many
features in DADE. What are you trying to do?

If you are trying to realias the available tables to the end user, then use
our DataDictionary component.


Cheers,

Jim Bennett
Digital Metaphors

rbuser

Jim Bennett (Digital Metaphors) wrote:

Jim, you ask tough questions. I'm developing a wizard which allows
the end user to drag 'n drop tables onto a pane, specify joins, etc. The
problem *was* that when I added the 'CUSTOMER' table twice, both
TdaTable objects would have 'CUSTOMER' in the Alias, RawTableName,
SQLAlias, and TableAlias properties which surprised me - I was expecting
that one of these properties would have 'CUSTOMER_2' or similar. And in
fact, I just tested it now, and the SQLAlias does indeed do that. Either
I accidently fixed a bug in my code, or perhaps I was imagining
things... At any rate, thanks for your help.

Ed Vander Hoek

digitalmetaphors

I do ask tough questions. The reason for this is because questions about the
source mean one of two things. 1. You know exactly why you need to know
about undocumented properties in the source, or 2. You haven't examined all
solutions and are facing problema we have solved with alternate techniques.
I want to make sure you are aware of the other possibilities before trying
to solve the problem you are running into. Knowing what your goal is helps
me understand how to better point you in the right direction. Either way,
glad to hear it is working. DADE should be aliasing as you've are seeign it
now. You wizard should create the objects on the TdaSQL object and it
should generate the MagicSQL the same as if you created the TdaSQL objects
using our DADE query tools.


Cheers,

Jim Bennett
Digital Metaphors