× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Jim, Adam and Rob (those who so far answered my first post on this thread), thanks for your answers.
- No, we did not trace ODBC. The fact, nevertheless, after much work and testing, that redefining the P15,5 fields as either F8/5 or P13/3 and then it works, I think makes it quite ckear.
- DSN was configured to use "*SYS" naming convention instead of "*SQL" convention, so using Library/File naming is correct, and works as expected.
- The main question is, does VB support 15/5? As I pointed in my first post, the ClientAccess Win95 ODBC manual seems to accept any available formats... No restrictions are shown. And, as I mentioned before, had no problems accessing any of these files/fields from MS/Word, MS/Access, MS/Query, which (if I'm not wrong...) use VBA for their access to foreign data.
Rob, APAR II07907 you mentioned, obviously, seems to imply, somehow, the fact that 15,5 is kind of a "strange" accuracy when defining data fields, but is it or is it not a real limitation to VB , if MS/Word, Access, Query work fine?


I still have same question. Why is 15/5 special for VB (but not for other MS products mentioned) but Floating8/5 or Packed 13/3 work fine? Anybody knows?
Thanks.


--
Antonio Fernandez-Vicenti
afvaiv@xxxxxxxxxx




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.