I haven't had to do this before, and halfway through, I realized I may be
taking the wrong approach here, so please allow me to drain your more
experienced brains a bit...
Scenario: Access 2003 with ODBC Linked Oracle Tables (Oracle Ora9i ODBC
Driver)
I'm building a dynamic SQL query such that the source Oracle tables have
three name fields (first, middle, last), but we want to show a single
concatenated name field for selection display purposes.
For a native JET query, I would simply put something like this together:
SELECT (blah blah)..., Nz([tbl].[firstname], '') &
iif(len(nz([tbl].[middlename], '')) > 0, ' ', '') & ... as DisplayName,
...
However, since I'm dealing with an ORACLE ODBClink (one that MAY need to
run
over a WAN link, at that), I'm wondering if I'm shooting myself in the
foot,
performance-wise, by trying to do that in a case like this.
Is there a better way to construct my selection query so that I don't put
myself in a world of hurt, performance-wise, as I execute this type of
selection query?
What alternatives do I have to the above approach...?
....perhaps run my query to neaten up the names on a sub-query which just
pulls the fields directly from oracle with no extra stuff involved
first...?
or some other thoughts...?
Should I be trying to do this via an ODBCDirect connection instead (for
above performance reasons)? If so, How can I accomplish the DisplayName
neatening-up trick if Oracle will be chewing on the SQL instead of Jet...?
|
