Can Visio connect to Acces db query with expression field?

I am trying to link a shpae's property (in this case,
it's text) to a field returned from an Access 2002
query. The shape should look up a record based on the
values in two fields, and return the value in a third
field that is actually an expression in the query. This
expression calls an internal (inside the Access DB) VBA
function that outputs a string that is the concatenation
of from 0 to 3 or 4 related text fields.

When I try to use the wizard, or edit the shapesheet
User.ODBCConnection formula directly to specify the query
name and fields, I get an ODBC error:
"ODBC Error: 37000
[Microsoft][ODBC Microsoft Access Driver] Undefined
function 'ConcatTechnologies' in expression."
The undefined function identified is in fact the name of
the function in the query's expression. This is the
ODBCConnection formula:
="ODBCDataSource=MS Access
Database|ODBCQualifier=C:\Documents and Settings\isaksp00
\My Documents\Architecture\App
Portfolio\Portfolio|ODBCTable=qryAllTechnologiesby AppbyCom
ponent|2|Source ID=Prop.SourceID1|Component
ID=Prop.ComponentTechnology|1|AllTechs=Shape.Text= 0|"

The query field named 'AllTechs' is the one that contains
the function call.
Can Visio in fact do this, or is it a limitation (that
you can not return data from query fields containing user
defined functions)?

in my experience odbc doesn't like querying things where there is an
executable on the other side. I've often ended up moving the code into visio
and doing the work there. It's an ODBC error, not visio.
Al
"isaksp00" wrote in message
...
I am trying to link a shpae's property (in this case,
it's text) to a field returned from an Access 2002
query. The shape should look up a record based on the
values in two fields, and return the value in a third
field that is actually an expression in the query. This
expression calls an internal (inside the Access DB) VBA
function that outputs a string that is the concatenation
of from 0 to 3 or 4 related text fields.

When I try to use the wizard, or edit the shapesheet
User.ODBCConnection formula directly to specify the query
name and fields, I get an ODBC error:
"ODBC Error: 37000
[Microsoft][ODBC Microsoft Access Driver] Undefined
function 'ConcatTechnologies' in expression."
The undefined function identified is in fact the name of
the function in the query's expression. This is the
ODBCConnection formula:
="ODBCDataSource=MS Access
Database|ODBCQualifier=C:\Documents and Settings\isaksp00
\My Documents\Architecture\App
Portfolio\Portfolio|ODBCTable=qryAllTechnologiesby AppbyCom
ponent|2|Source ID=Prop.SourceID1|Component
ID=Prop.ComponentTechnology|1|AllTechs=Shape.Text= 0|"

The query field named 'AllTechs' is the one that contains
the function call.
Can Visio in fact do this, or is it a limitation (that
you can not return data from query fields containing user
defined functions)?

Thanks, Al. I later tried doing a query from Excel, using MS Query, and got
much the same result - so it is broader than Visio. I would have thought
that, code or no code, accessing a query would return the data viewed in the
query just as if it were a physical table - seems not to be so. I don't want
to have to learn the Visio VBA object model, so I'll see if there are any
other solutions...

"Al Edlund" wrote:

in my experience odbc doesn't like querying things where there is an
executable on the other side. I've often ended up moving the code into visio
and doing the work there. It's an ODBC error, not visio.
Al

I haven't dug into it real deep, but, the suspicion is the data and query
are pulled across to the client side and the executables are not. That's
what causes the disconnect.
al
"Peter I" Peter wrote in message
...
Thanks, Al. I later tried doing a query from Excel, using MS Query, and
got
much the same result - so it is broader than Visio. I would have thought
that, code or no code, accessing a query would return the data viewed in
the
query just as if it were a physical table - seems not to be so. I don't
want
to have to learn the Visio VBA object model, so I'll see if there are any
other solutions...

"Al Edlund" wrote:

in my experience odbc doesn't like querying things where there is an
executable on the other side. I've often ended up moving the code into
visio
and doing the work there. It's an ODBC error, not visio.
Al