Subject: | |
From: | |
Reply To: | |
Date: | Wed, 23 Apr 1997 22:33:23 GMT |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
In article <[log in to unmask]>, Rob McEwan
<[log in to unmask]> writes:
>Any answers/comments on the following will be mostly appreciated:
>
>(1) What OS version/ patch do I need to be on to test the MB Foster
>limited version ODBC drivers? My information is 5.5 plus a pull patch
>for MBF ODBC.
>
>(2) What problems have you run in to re. MBF's ODBC vs. HP's in Visual
>Basic (v3)? I ran into a brick wall while looking at a demo last year
>where MB was returning a null for a blank string whereas HP returned a
>single space (string$=null causes runtime error in VB). In other words,
>am I going to have a smooth transition from HP to MB ODBC???
>
>
>
Rob - I am assuming you are referring to the ODBCLink/SE product that HP
is bundling as part of the Image/SQL product. This product will run fine
on MPE5.5
but does require version B.G1.10 or later of Image/SQL and AllBase Version
A.G1.15 or later.
The VB (version 3) problem of returning a null instead of a blank was
fixed several versions ago ...
the ODBCLink/SE code is from a common source with the DataExpress/ODBCLink
having more features like KSAM, MPE, and Powerhouse support ... the
transition from the HP-PCAPI has been smoothed by the inclusion of the DSN
Migration ulitiy which will convert existing datasources to those that
ODBCLink/SE will work with.
If you have any more questions on DataExpress and ODBCLink please contact
us
at Info @ MBFOSTER.COM - or for specific technical questions at
[log in to unmask]
Best regards,
Birket Foster
Birket Foster
M. B. Foster Associates .. the 1-800-ANSWERS people!
(613) 448-2333 or (613) 448-2588 (FAX)
(Thanks for your support of our 32bit DataExpress ODBCLink Driver)
|
|
|