![]() |
|||||||||||||||||
|
|
|||||||||||||||||
|
|
|||||||||
|
Company
|
SQL LINKS DEVELOPER SUPPORT
SEARCH Borland Online/Developer Support
CLIENT ACCESS ODBC DRIVER (32BIT)
V0.00.0000
5/9/96
CWBODBC.DLL
Delphi 2.0
BDE 3.0/ODBC Socket
PROBLEM:
Using DBD 7.0:
File | Open | Table, pick alias, pick table:
"IBM client access ODBC driver (32bit) (db2/400 sql)
sql5016 object name fcdrcust not valid for naming option"
Using a Delphi 2.0 TQuery:
SELECT * FROM PGEDTA.FCDRCUST
TQuery could be made active but not display data
(Information here is sketchy. The customer may not have
been doing this correctly. I concentrated on passing SQL
and opening tables via the DBD.)
General information:
1)After the changes mentioned below (SQL NAMING CONV. and
SCROLLABLE CURSOR) were made to the Client Access ODBC DSN
Delphi 2.0 displayed tables using dot notation ie:
PGEDTA.FCDRCUST (LIBRARY.TABLENAME) and tables could be
opened *with* data displayed in both a Delphi 2.0 app and
DBD 7.0.
2)AS/400 is not case sensitive.
3)correct SQL passthrough syntax TBD (customer Larry Scott
PIN# 1318114 will provide addtional info via email)
ODBC DRIVERS OPTIONS (using the ODBC32 MANAGER that may only
be in the Client Access group/directory):
**SQL NAMING CONVENTION (X)/ SYSTEM NAMING CONVENTION**
(make sure that you are using "SQL NAMING CONVENTION")
**SCROLLABLE CURSOR**
Set your scrollable cursor to
"Always scrollable". (Client Access ODBC Setup, Other
page, Scrollable cursor option)
Relevent info from:
IBM's COMMON COMPLAINTS ABOUT THE (Client Access) ODBC DRIVER
** Last updated 5/23/96 **
Complaint:
"Once I connect to the AS/400 I can't see any libraries."
Workaround:
Set your default library list to include the libraries
you want. (Client Access ODBC Setup, Server page,
Default libararies option)
-------------------
Complaint:
"When I open a table, it appears to be empty even though
there is data in it."
Workaround:
It is likely that your application is trying to open the
table for update but it can't, so it just displays an
empty grid. Look at the Client Access Online User Guide
under "Troubleshooting ODBC Problems" section
"ODBC - Enabling tables to be updated".
(**the option below enabled BDE 3.0 to "see" data in data
stored in a table on the AS/400**)
Another possible explanation for incomplete data is that
the application is trying to use a scrollable cursor with
a rowset size of 1. Set your scrollable cursor to
"Always scrollable". (Client Access ODBC Setup, Other
page, Scrollable cursor option)
More info can be found on IBM's web site:
www.as400.ibm.com IBM's AS400 site.
PUB
ODBC BDE ERROR
BC, IBM
|
|
|
|
|||||
| Made in Borland® Copyright© 1994-2003 Borland Software Corporation. All rights reserved. Report Piracy, Legal Notices, Privacy Policy Last Modified Monday, 26-Mar-2001 16:27:08 PST |
|||||