Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.os.os2.programmer.misc > #1497

Re: VisproRexx odbc

From "A.D. Fundum" <what.ever@neverm.ind>
Message-ID <dWF0uWVMuGJo-pn2-wNtfSPFj4Zc9@localhost> (permalink)
Newsgroups comp.os.os2.programmer.misc
Subject Re: VisproRexx odbc
References (3 earlier) <137f51df-c42b-450e-bcfe-bfcb8806e226@googlegroups.com> <dWF0uWVMuGJo-pn2-dYCihwGhqoeU@localhost> <0361d5e7-bfa5-40b2-9022-b0d1b8a1d995@googlegroups.com> <dWF0uWVMuGJo-pn2-OqVq3J2yIPp3@localhost> <f7d1e271-1914-4b13-b6b2-453ab94af121@googlegroups.com>
Organization XS News
Date 2015-12-03 12:36 +0100

Show all headers | View raw


 > Please send me an e-mail and I'll be happy to provide necessary 
files.

Which version of VPR are you using?

It's not unlikely that your last ODBC 3-discovery is important, but 
just reporting error messages doesn't help other people helping you. 
People will, for example, assume that the fatal error "cannot 
find/load" is produced by the interpreter.

But it's also possible that one succesfully (and checked!!!) function 
produces the non-fatal warning, so a next phase still populates 
tables. 

Ignoring an overload of tracing, you could have added code to debug 
the issue and to check for detectacle errors. To help people helping 
you. The number of users of both VPR and ODBC will be limited. So 
people will be answering in "general mode", including the assumption 
that you are using their bleeding ooRexx-interpreter for Windows.

By the way, I'm not going to try if I can use an ODBC DLL of that 
other Rexx interpreter.

 > my Google account a valid e-mail address got displayed on my posts.

That;'s just scratching the surface of Google sharing personal data, 
without the user being fully aware of that...


--

Back to comp.os.os2.programmer.misc | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

VisproRexx odbc per@raiko.no - 2015-10-22 06:06 -0700
  Re: VisproRexx odbc per@raiko.no - 2015-11-20 06:09 -0800
  Re: VisproRexx odbc per@raiko.no - 2015-11-20 07:43 -0800
    Re: VisproRexx odbc "A.D. Fundum" <what.ever@neverm.ind> - 2015-11-21 11:13 +0100
      Re: VisproRexx odbc per@raiko.no - 2015-11-21 11:01 -0800
        Re: VisproRexx odbc "A.D. Fundum" <what.ever@neverm.ind> - 2015-11-23 08:46 +0100
          Re: VisproRexx odbc PJ <per@raiko.no> - 2015-11-24 13:04 -0800
            Re: VisproRexx odbc "A.D. Fundum" <what.ever@neverm.ind> - 2015-11-25 19:04 +0100
              Re: VisproRexx odbc PJ <per@raiko.no> - 2015-11-25 11:12 -0800
                Re: VisproRexx odbc "A.D. Fundum" <what.ever@neverm.ind> - 2015-12-03 12:36 +0100
                Re: VisproRexx odbc PJ <per@raiko.no> - 2015-12-03 06:45 -0800
  Re: VisproRexx odbc "A.D. Fundum" <what.ever@neverm.ind> - 2015-12-05 17:28 +0100

csiph-web