Kbase 17266: ODBC Dataserver testing template to narrow problem down
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
2/12/1999 |
|
ODBC Dataserver testing template to narrow problem down
This is an overview of what is needed to troubleshoot WebSpeed
and ODBC Dataserver issues. There are basically 3 steps that
have to be verified. This is designed similarly to the SpeedStart
test that was done for the WebSpeed 2 product.
The problem with complex configuration issues is that it is
difficult to determine where the problem lies. This set of tools
will assist in problem determination.
Step 1 is to verify that you can connect to the schema holder
without going any further down the path. This should return a
message that it was successful or unsuccessful. An example to
test this follows.
for each _DB where _DB._db-name ne ? no-lock:
display _DB._db-name _DB._db-type _DB._db-local.
end.
Step 2 is to verify the ODBC connection to the database without
Progress involved at all. This can be handled by the ODBC driver
company. They generally provide the customer with a
listing of how to test this connection.
An example of this is a demo program called cppdmo32 that
ships with the Microsoft ODBC 2.0 Resource Kit.
Step 3 is to verify access to the database through the schema holder
and the ODBC driver. This can be 4gl code and should be in 2 steps:
1) reading the data out of the database, and
2) updating the data in the database.
Here is an example of what could be done:
def var a as char format "x(30)".
def var b as char format "x(30)".
def var c as char format "x(30)".
find first _file where _file-number gt 0 no-lock.
a = _file-name.
output to two.p.
b = "find first " + a + " no-lock. ".
c = "update " + a + ".".
display b skip c with frame a no-labels.
display skip "return." no-label.
output close.
run two.p.
These three steps should identify where the problem lies and make it
much easier to solve the issue.
Progress Software Technical Support Note # 17266