IM Deployment and Library Search Path - cause of SQLSTATE 37000?

[Peter Barth]

IM 11.2 Build 8542

Client Windows XP SP2
Server MS 2008 Standard Server
Terminal Server Windows 2003 R2 SP2

When developing IM pbl/executables, we regularly employ a ddw.pbl (for
dropdown data windows) which may be re-used by all other pbl/executables in
the library. Typically, the ddw.pbl never gets compiled to an executable -
there is no need for this.

Such ddw.pbl is made available to other pbls through an entry in the IM
Library List window (specifying the path and the library name to be shared).

When we deploy the IM executables of our application, they will invariably
fail on SQLSTATE 37000 - when it comes to the use of Drop Down Data Windows
(which have been defined in the ddw.pbl).

I was under the impression, that these references to and their query code of
ddw.pbl entries will be included into the executables of the application -
but this may be a wrong assumption on my part.

Anybody knows, how we can ship around this problem? Pls. do not suggest that
we simply include the (over 1000) entries of the ddw.pbl into every other of
the (about 80 pbls.

We included the ddw.pbl in the same path were the executables are - but this
does not work.

How can we make the executables make to know, where the missing references
can be found?

Your help is very much appreciated.

Kind regards

Peter W. Barth

[Arnd Schmidt]

Peter,

I doubt this is a PBL/PDB Problem.
Did you already made a ODBC Trace, so that you can see what causes the error?

I had a problem like this using PB 9 and ASA9 some weeks ago,
when Sybase Workspace switched the QUOTED_IDENTIFIER
option for the user.

The solution was to check the OPTION QUOTED_IDENTIFIER
option of the database and the Connection Properties ("DelimitIdentifier")
displayed as "Enclose Table and Column Names in quotes" in the
Database profile's "Syntax" tab.

hth

Arnd

Post by Peter Barth
IM 11.2 Build 8542
Client Windows XP SP2
Server MS 2008 Standard Server
Terminal Server Windows 2003 R2 SP2
When developing IM pbl/executables, we regularly employ a ddw.pbl (for
dropdown data windows) which may be re-used by all other pbl/executables in
the library. Typically, the ddw.pbl never gets compiled to an executable -
there is no need for this.
Such ddw.pbl is made available to other pbls through an entry in the IM
Library List window (specifying the path and the library name to be shared).
When we deploy the IM executables of our application, they will invariably
fail on SQLSTATE 37000 - when it comes to the use of Drop Down Data Windows
(which have been defined in the ddw.pbl).
I was under the impression, that these references to and their query code of
ddw.pbl entries will be included into the executables of the application -
but this may be a wrong assumption on my part.
Anybody knows, how we can ship around this problem? Pls. do not suggest that
we simply include the (over 1000) entries of the ddw.pbl into every other of
the (about 80 pbls.
We included the ddw.pbl in the same path were the executables are - but this
does not work.
How can we make the executables make to know, where the missing references
can be found?
Your help is very much appreciated.
Kind regards
Peter W. Barth