Conference orarep::nomahs::odbc_rdb_driver

1311.0. "OLE object or long binary data alternatives" by BROKE::BITHER () Tue Mar 11 1997 16:43

Hi,

I have a customer who is encountering what I believe to be expected behavior
but am wondering if anyone can suggest some alternatives for him?

PROBLEM:

MSA 2.0, ODBC 2.09, Rdb.

Has tables in Rdb with fields of type list of byte varying.  Segment size
is 128 so assuming fields are defined as list of byte varying (128).
In his configuration, odbc is treating the fields as binary and MSA
sees them as ole objects.  When he opens a table with such a field
the field says "long binary data" instead of the actual data.

In my configuration, MSA 7.0, ODBC 2.1, I get the same results except
the field says "OLE Object."  I believe this is due to a higher version
of MS Access.

ANALYSIS:

How can he see such a field using this interface?  Does it even make sense
given the unknown size of such a field?  I tried doing this with
passthru SQL (got it to work w/interactive SQL):

   begin
   declare aaa table cursor for select employee_id, resume from resumes
   where employee_id='00166';
   open aaa;
   fetch aaa;
   declare bbb read only scroll list cursor for select resume where
   current of aaa;
   open bbb;
   fetch first from bbb;
   fetch next from bbb;
     etc.
   end

Set removecontrolchars to "YES" so don't get illegal char but still get
syntax errors.  Using begin/end to get around syntax errors by use of
semicolons but doesn't work.

Can anyone recommend a way to display this data to a user of MS Access.
If not, can anyone recommend another application that is good for generating
reports that can be used to display this data?  Customer is primarily 
interested in report generation.

Thanks, Diane

>How can he see such a field using this interface?  Does it even make sense

can't help here cuz i don't drive access that well, but "OLE Object" is MSA
for an rdb list of byte.

>Set removecontrolchars to "YES" so don't get illegal char but still get
>syntax errors.  Using begin/end to get around syntax errors by use of
>semicolons but doesn't work.

This I can clear up for you.
the syntax errors are because you can't have open/fetch cursor in a begin
end block.  cursors are not supported in a compound statement.

    Sounds like a question for Microsoft...
    
    John